From 7daa6708d2afc710bebbb2dc30f4371f9d67120c Mon Sep 17 00:00:00 2001 From: Dan McGee Date: Wed, 27 Jun 2007 23:25:04 -0400 Subject: Remove lockfile configuration from frontend, make it job of libalpm I previously introduced some patches to make just about every path in pacman/libalpm configurable; doing this with the lockfile seemed a bit too far and we really should just place the lockfile where it belongs- with the DB that needs locking. More details in this thread: http://archlinux.org/pipermail/pacman-dev/2007-June/008499.html Signed-off-by: Dan McGee --- scripts/pacman-optimize.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'scripts') diff --git a/scripts/pacman-optimize.in b/scripts/pacman-optimize.in index 3f7f51f7..d4c926d8 100644 --- a/scripts/pacman-optimize.in +++ b/scripts/pacman-optimize.in @@ -27,7 +27,7 @@ export TEXTDOMAINDIR='@localedir@' myver='@PACKAGE_VERSION@' dbroot='@localstatedir@/lib/pacman/' -lockfile='@localstatedir@/run/pacman.lck' +lockfile="${dbroot}db.lck" msg() { local mesg=$1; shift -- cgit v1.2.3-24-g4f1b