Next | Query returned 54 messages, browsing 51 to 60 | previous

History of commit frequency

CVS Commit History:


   2005-02-24 14:10:14 by Alistair G. Crooks | Files touched by this commit (192)
Log message:
Add RMD160 digests.
   2005-02-19 11:35:00 by Thomas Klausner | Files touched by this commit (2)
Log message:
[Changes for 0.44 - 2004-12-16]

* Add "pmfiles.dat" to legacy manifest_skip routine to accomodate
  early Win32 hacks.  Reported by Steve Hay via Michael Schwern.

[Changes for 0.43 - 2004-12-16]

* Updated t/0-signature.t to be more friendly with Test::More;
  contributed by Michael Schwern.

* Add $Timeout (default 3 seconds) to control the timeout for
  probing connections to the key server.

* Take account of the .ts files produced by newer MakeMakers
  in the suggested MANIFEST.SKIP list.

[Changes for 0.42 - 2004-11-20]

* Move under SVK version control management; ditch keyword tags.

* Michael Schwern pointed out that during development, the
  "signature.t" file would keep failing.

* Documented how to generate SIGNATURE files as part of "make dist",
  for Module::Install, ExtUtils::MakeMaker and Module::Build users .
   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-11 19:11:58 by Stoned Elipot | Files touched by this commit (5) | Imported package
Log message:
Initial addition of p5-Module-Signature version 0.41 in the NetBSD Packages
Collection.

The Perl 5 module Module::Signature adds cryptographic authentications
to CPAN distributions, via the special SIGNATURE file.

If you are a module user, all you have to do is to remember running
cpansign -v (or just cpansign) before issuing perl Makefile.PL or
perl Build.PL; that will ensure the distribution has not been
tampered with.  For module authors, you'd want to add the SIGNATURE
file to your MANIFEST, then type cpansign -s before making a
distribution. You may also want to consider adding a signature
check as part of your test suite.


Next | Query returned 54 messages, browsing 51 to 60 | previous