Next | Query returned 37 messages, browsing 31 to 40 | previous

History of commit frequency

CVS Commit History:


   2005-08-06 08:19:41 by Johnny C. Lam | Files touched by this commit (634) | Package updated
Log message:
Bump the PKGREVISIONs of all (638) packages that hardcode the locations
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 20:01:49 by Johnny C. Lam | Files touched by this commit (578)
Log message:
Turn PERL5_PACKLIST into a relative path instead of an absolute path.
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 23:48:17 by Todd Vierling | Files touched by this commit (3539)
Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.
   2005-02-24 10:59:30 by Alistair G. Crooks | Files touched by this commit (177)
Log message:
Add RMD160 digests.
   2004-12-20 12:31:14 by grant beattie | Files touched by this commit (467)
Log message:
since perl is now built with threads on most platforms, the perl archlib
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 03:19:20 by Todd Vierling | Files touched by this commit (3)
Log message:
Update to 0.31.  Fix HOMEPAGE (moved).

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 21:49:04 by Todd Vierling | Files touched by this commit (5) | Imported package
Log message:
Moved from pkgsrc-wip (http://pkgsrc-wip.sourceforge.net/):

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.


Next | Query returned 37 messages, browsing 31 to 40 | previous