pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2005-01-18	Enable on Interix.	tv	1	-2/+2

2004-01-20	Move WRKSRC definition away from the first paragraph in a Makefile.	agc	1	-2/+2

2003-07-21	COMMENT should start with a capital letter.	martti	1	-2/+2

2003-07-17	s/netbsd.org/NetBSD.org/	grant	1	-2/+2

2003-06-02	Use tech-pkg@ in favor of packages@ as MAINTAINER for orphaned packages.	jschauma	1	-2/+2
	Should anybody feel like they could be the maintainer for any of thewe packages, please adjust.
2003-03-29	Place WRKSRC where it belongs, to make pkglint happy; ok'ed by wiz.	jmmv	1	-2/+2

2002-02-15	Set empty DISTFILES so no fetch is really attempted.	seb	2	-3/+16
	Unconditionally set PKGSRC_LOCKTYPE to `none' to avoid bootstrapping problem. Do not generate formatted manual and do not install source manual on Solaris or else we would need to make this package depends on textproc/groff. IMHO this should be avoided for this package as it can be considered a prerequisite for building further packages.
2002-01-15	Initial import of Erik E. Fair's shlock utility, with sources taken from	agc	6	-0/+526
	NetBSD-current, into the NetBSD Packages Collection. The shlock command can create or verify a lock file on behalf of a shell or other script program. When it attempts to create a lock file, if one already exists, shlock verifies that it is or is not valid. If valid, shlock will exit with a non-zero exit code. If invalid, shlock will re- move the lock file, and create a new one. shlock uses the rename(2) system call to make the final target lock file, which is an atomic operation (i.e. "dot locking", so named for this mech- anism's original use for locking system mailboxes). It puts the process ID ("PID") from the command line into the requested lock file. shlock verifies that an extant lock file is still valid by using kill(2) with a zero signal to check for the existence of the process that holds the lock. This package is only for Solaris and Linux platforms at present.