diff options
| author | jlam <jlam> | 2006-07-06 22:08:32 +0000 |
|---|---|---|
| committer | jlam <jlam> | 2006-07-06 22:08:32 +0000 |
| commit | 44f7dcbfb4e3153be7db0bb2b0d6914ddb96f8a7 (patch) | |
| tree | 607fe264a55f0893e0b68c2a4bee1da930fb64d3 /mk/bsd.pkg.barrier.mk | |
| parent | a40b1ca6bffaa2683425454a683531aac0ab0781 (diff) | |
| download | pkgsrc-44f7dcbfb4e3153be7db0bb2b0d6914ddb96f8a7.tar.gz | |
The "replace" target does conceptually the same thing as the "install"
target in that it installs the currently-built software into the
filesystem. In that case where "replace" is specified as a target on
the command line, make "replace" and not "install" be the source target
for "package".
Also, place the "replace" target between the "install" and "package"
targets in _BARRIER_POST_TARGETS as it should be legal to do those
steps in that order (but not in another order).
These changes make the following work:
make replace package
In this example, the currently installed package will be replaced and
the newly-installed software will be packaged, all within the same
make process.
Diffstat (limited to 'mk/bsd.pkg.barrier.mk')
| -rw-r--r-- | mk/bsd.pkg.barrier.mk | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/mk/bsd.pkg.barrier.mk b/mk/bsd.pkg.barrier.mk index dfb4528c75d..54631f6645d 100644 --- a/mk/bsd.pkg.barrier.mk +++ b/mk/bsd.pkg.barrier.mk @@ -1,4 +1,4 @@ -# $NetBSD: bsd.pkg.barrier.mk,v 1.3 2006/07/06 15:43:10 jlam Exp $ +# $NetBSD: bsd.pkg.barrier.mk,v 1.4 2006/07/06 22:08:32 jlam Exp $ _BARRIER_COOKIE= ${WRKDIR}/.barrier_cookie @@ -19,12 +19,10 @@ _BARRIER_POST_TARGETS+= test _BARRIER_POST_TARGETS+= all _BARRIER_POST_TARGETS+= install _BARRIER_POST_TARGETS+= reinstall +_BARRIER_POST_TARGETS+= replace _BARRIER_POST_TARGETS+= package _BARRIER_POST_TARGETS+= repackage -# XXX This target should probably be handled specially. -_BARRIER_POST_TARGETS+= replace - .for _target_ in ${_BARRIER_POST_TARGETS} . if make(${_target_}) _BARRIER_CMDLINE_TARGETS+= ${_target_} |