pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2007-10-25	Remove empty PLISTs from pkgsrc since revision 1.33 of plist/plist.mk	jlam	1	-1/+0
	can handle packages having no PLIST files.
2007-03-19	give away to pkgsrc-users	tv	1	-2/+2

2006-03-22	Use "tv@NetBSD.org" as my MAINTAINER address; makes identifying me as a	tv	1	-2/+2
	PR-responsible person (such as I am ;) a little easier.
2005-08-06	Bump the PKGREVISIONs of all (638) packages that hardcode the locations	jlam	1	-3/+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 digests.	agc	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-11-29	Update to 0.31. Fix HOMEPAGE (moved).	tv	3	-15/+10
	Notable changes (no changelog to speak of): - added srsc command line client to srsd - fixed upper/lower case comparisons in domain matching
2004-03-29	Moved from pkgsrc-wip (http://pkgsrc-wip.sourceforge.net/):	tv	5	-0/+70
	The Sender Rewriting Scheme preserves .forward functionality in an SPF-compliant world. SPF requires the SMTP client IP to match the envelope sender (return-path). When a message is forwarded through an intermediate server, that intermediate server may need to rewrite the return-path to remain SPF compliant. If the message bounces, that intermediate server needs to validate the bounce and forward the bounce to the original sender. SRS provides a convention for return-path rewriting which allows multiple forwarding servers to compact the return-path. SRS also provides an authentication mechanism to ensure that purported bounces are not arbitrarily forwarded.