On Sat, Jun 02, 2007 at 06:21:37PM +0200, Marc Espie wrote: > On Sat, Jun 02, 2007 at 08:21:14AM -0400, Josh Grosse wrote: > > On Sat, Jun 02, 2007 at 02:10:44PM +0200, Marc Espie wrote: > > > Does anyone out there uses a lock command that's not the `default' one > > > in infrastructure/build/dolock ? > > > > Does /usr/bin/touch count as non-default? For several years, I've been > > using that, as ports(7) says to assign LOCK_CMD a value along with LOCKDIR > > and UNLOCK_CMD. > Yes, touch counts as non-default. Plus, touch is bogus. It doesn't lock > anything.
And I'll respond to my own post to note that ports(7) is not all that clear, especially when the LOCK_CMD/UNLOCK_CMD description actually lives in bsd.port.mk(5), so I've just amended the manpage. Usually, you only need to define LOCK_DIR to have working locks. I've briefly experimented with various methods before putting the locking script in the infrastructure at some point, and I've solved the recursive locking issues later. These days, most locks will work with infrastructure/build/dolock, except for very bizarre file system configurations.
