pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2016-07-09	Bump PKGREVISION for perl-5.24.0 for everything mentioning perl.	wiz	1	-2/+2

2015-11-03	Add SHA512 digests for distfiles for devel category	agc	1	-1/+2
	Issues found with existing distfiles: distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip distfiles/fortran-utils-1.1.tar.gz distfiles/ivykis-0.39.tar.gz distfiles/enum-1.11.tar.gz distfiles/pvs-3.2-libraries.tgz distfiles/pvs-3.2-linux.tgz distfiles/pvs-3.2-solaris.tgz distfiles/pvs-3.2-system.tgz No changes made to these distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-06-12	Recursive PKGREVISION bump for all packages mentioning 'perl',	wiz	1	-2/+2
	having a PKGNAME of p5-*, or depending such a package, for perl-5.22.0.
2014-05-29	Bump for perl-5.20.0.	wiz	1	-2/+2
	Do it for all packages that * mention perl, or * have a directory name starting with p5-, or depend on a package starting with p5- like last time, for 5.18, where this didn't lead to complaints. Let me know if you have any this time.
2013-05-31	Bump all packages for perl-5.18, that	wiz	1	-2/+2
	a) refer 'perl' in their Makefile, or b) have a directory name of p5-, or c) have any dependency on any p5- package Like last time, where this caused no complaints.
2012-10-31	Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.	asau	1	-3/+1

2012-10-03	Bump all packages that use perl, or depend on a p5-* package, or	wiz	1	-1/+2
	are called p5-*. I hope that's all of them.
2008-09-17	Remove unused doc installation target.	bjs	1	-5/+1

2008-09-11	Import cvsutils-0.2.5; package originally created by	bjs	5	-0/+58
	<pancake@phreaker.net>. CVS Utilities is a set of scripts that operate on working directories of CVS (Concurrent Versions System). Unlike some other version control systems, it's common for CVS repository to reside on a remote system. Unfortunately, the standard CVS client requires connection to the repository for almost all operations. This means that some operations are impossible when the repository is unreachable over the network, or when the network connection is slow compared to the size of the project. In fact, CVS keeps some data in the working directory that allows for some disconnected operations. In particular, no connection to the repository is required to identify locally modified files. But the CVS client cannot do it. This is the gap CVS Utilities aim to close. Admittedly, the insistence of the CVS client on repository connection can be justified in most cases. That's why CVS Utilities are not aiming to be a "better client". It's an extension to CVS client with limited capabilities but higher speed. (If someone was to write a better CVS client, it would probably keep base versions or their checksums somewhere, like Subversion does, but CVS Utilities use the same format of the working directory as the standard CVS client.)