pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2006-06-02	Rename all PHP 4 packages to php4-, all PHP 5 packages to php5-,	joerg	1	-2/+2
	all PEAR packages to php?-pear-* and all Apache packages to ap13-* or ap2-* respectively. Add new variables to simplify the Makefile handling. Add CONFLICTS on the old names. Reset revisions of bumped packages. ap-php will now depend on the default Apache and PHP version. All programs using it have an implicit option of the Apache version as well. OK from jlam@ and adrianp@.
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.
2006-02-05	Recursive revision bump / recommended bump for gettext ABI change.	joerg	1	-2/+2

2006-01-24	Bump BUILDLINK_RECOMMENDED of textproc/expat to 2.0.0 because	wiz	1	-2/+2
	of the shlib major bump. PKGREVISION++ for the dependencies.
2005-08-06	Bump the PKGREVISIONs of all (638) packages that hardcode the locations	jlam	1	-2/+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-04-11	Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.	tv	1	-2/+1

2005-02-24	Add RMD160 checksums.	wiz	1	-1/+2

2004-12-20	since perl is now built with threads on most platforms, the perl archlib	grant	1	-1/+2
	module directory has changed (eg. "darwin-2level" vs. "darwin-thread-multi-2level"). binary packages of perl modules need to be distinguishable between being built against threaded perl and unthreaded perl, so bump the PKGREVISION of all perl module packages and introduce BUILDLINK_RECOMMENDED for perl as perl>=5.8.5nb5 so the correct dependencies are registered and the binary packages are distinct. addresses PR pkg/28619 from H. Todd Fujinaka.
2004-05-09	Convert to buildlink3.	snj	1	-3/+3

2003-07-22	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.
2002-10-27	Use buildlink2. Use perl5/module.mk.	seb	1	-7/+4

2001-11-26	Buildlinkify, in the sense that only the perl headers are found in	jlam	1	-3/+4
	${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
2001-11-01	Move pkg/ files into package's toplevel directory	zuntum	3	-1/+1

2001-10-18	SVR4 packages have a limit of 9 chars for a package name.	veego	1	-1/+2
	The automatic truncation in gensolpkg doesn't work for packages which have the same package name for the first 5-6 chars. e.g. amanda-server and amanda-client would be named amanda and amanda. Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for amanda-server. All svr4 packages also have a vendor tag, so we have to reserve some chars for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6 or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the vendor tag enough room. All p5-* packages and a few other packages have now a SVR4_PKGNAME.
2001-10-01	p5-Apache-SSI - implements Server Side Includes in Perl	jlam	5	-0/+51
	Apache::SSI implements the functionality of mod_include for handling server-parsed html documents. It runs under Apache's mod_perl. In my mind, there are two main reasons you might want to use this module: you can sub-class it to implement your own custom SSI directives, and/or you can parse the output of other mod_perl handlers, or send the SSI output through another handler (use Apache::Filter to do this).