diff options
| author | jlam <jlam> | 2006-07-06 22:08:32 +0000 |
|---|---|---|
| committer | jlam <jlam> | 2006-07-06 22:08:32 +0000 |
| commit | 1389f360700eb69ad04937db0fe4a135c23d2f19 (patch) | |
| tree | 607fe264a55f0893e0b68c2a4bee1da930fb64d3 /mk/package | |
| parent | b5647ca8abd89b1c5e87915b633688d69a756244 (diff) | |
| download | pkgsrc-1389f360700eb69ad04937db0fe4a135c23d2f19.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/package')
| -rw-r--r-- | mk/package/package.mk | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/mk/package/package.mk b/mk/package/package.mk index 204fc7b1599..5a70008711c 100644 --- a/mk/package/package.mk +++ b/mk/package/package.mk @@ -1,4 +1,4 @@ -# $NetBSD: package.mk,v 1.11 2006/07/05 22:21:03 jlam Exp $ +# $NetBSD: package.mk,v 1.12 2006/07/06 22:08:32 jlam Exp $ ###################################################################### ### package (PUBLIC) @@ -7,7 +7,11 @@ ### acquire elevated privileges just-in-time. ### _PACKAGE_TARGETS+= check-vulnerable +.if make(replace) +_PACKAGE_TARGETS+= replace +.else _PACKAGE_TARGETS+= install +.endif _PACKAGE_TARGETS+= acquire-package-lock _PACKAGE_TARGETS+= ${_PACKAGE_COOKIE} _PACKAGE_TARGETS+= release-package-lock |