summaryrefslogtreecommitdiff
path: root/mk/install
diff options
context:
space:
mode:
authorrillig <rillig@pkgsrc.org>2006-08-03 19:12:42 +0000
committerrillig <rillig@pkgsrc.org>2006-08-03 19:12:42 +0000
commit7487a78a0ccf1b0e04f66848f47a50e9dd436c72 (patch)
treef9af6baecc7584970a853aa909ec225904d31679 /mk/install
parentcb8229e008dd2f2e3d735c997411a1fbe3622ffd (diff)
downloadpkgsrc-7487a78a0ccf1b0e04f66848f47a50e9dd436c72.tar.gz
When installing or deinstalling a package, it is not enough to lock the
WRKDIR against foreign processes. Instead, the PKG_DBDIR is locked, preventing other (pkgsrc) processes from modifying the set of installed packages while another one is doing that. This allows to use "bmake update" efficiently on multi-processor machines by just running it in four different package directories. Note that the pkg_add and pkg_delete tools may still interfere with this locking when they are directly run.
Diffstat (limited to 'mk/install')
-rw-r--r--mk/install/deinstall.mk4
1 files changed, 2 insertions, 2 deletions
diff --git a/mk/install/deinstall.mk b/mk/install/deinstall.mk
index de1dd90f10f..0f5423b6fe7 100644
--- a/mk/install/deinstall.mk
+++ b/mk/install/deinstall.mk
@@ -1,4 +1,4 @@
-# $NetBSD: deinstall.mk,v 1.3 2006/06/05 22:49:44 jlam Exp $
+# $NetBSD: deinstall.mk,v 1.4 2006/08/03 19:12:43 rillig Exp $
# DEINSTALLDEPENDS controls whether dependencies and dependents are also
# removed when a package is de-installed. The valid values are:
@@ -21,7 +21,7 @@ deinstall: su-target
@${PHASE_MSG} "Deinstalling for ${PKGNAME}"
.endif
-su-deinstall: deinstall-pkg install-clean
+su-deinstall: acquire-install-lock deinstall-pkg release-install-lock install-clean
MAKEFLAGS.su-deinstall= DEINSTALLDEPENDS=${DEINSTALLDEPENDS}