pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2006-03-04	Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no	jlam	1	-2/+2
	developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2005-11-23	Update to 1.101:	wiz	2	-7/+7
	1.101 Mon Oct 10 2005 - It appears I overtightened the naming rules. Reversed 1.100 Mon Oct 10 2005 - Significant version bump to announce addition of major functionality - Added Algorithm::Dependency::Weight - Upgraded a few remaining things to Params::Util 1.04 Wed Sep 14 2005 - Converted to Module::Install - Added Algorithm::Dependency::Source::HoA by request - Modernised the layout a little - Upgraded from UNIVERSAL::isa to Params::Util to support more complex uses of objects like Adapaters and Decorators.
2005-08-06	Bump the PKGREVISIONs of all (638) packages that hardcode the locations	jlam	1	-1/+2
	of Perl files to deal with the perl-5.8.7 update that moved all pkgsrc-installed Perl files into the "vendor" directories.
2005-07-13	Turn PERL5_PACKLIST into a relative path instead of an absolute path.	jlam	1	-2/+2
	These paths are now relative to PERL5_PACKLIST_DIR, which currently defaults to ${PERL5_SITEARCH}. There is no change to the binary packages.
2005-06-24	Fix PKGNAME.	wiz	1	-1/+2

2005-06-24	Initial import of p5-Algorithm-Dependency-1.03:	wiz	4	-0/+32
	Algorithm::Dependency is a framework for creating simple read-only dependency hierarchies, where you have a set of items that rely on other items in the set, and require actions on them as well. Despite the most visible of these being software installation systems like the CPAN installer, or debian apt-get, they are useful in other situations. This module intentionally uses implementation-neutral words, to avoid confusion.