<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/security/p5-Module-Signature, branch pkgsrc_2004Q4</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2004Q4</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2004Q4'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2004-12-20T11:30:55Z</updated>
<entry>
<title>since perl is now built with threads on most platforms, the perl archlib</title>
<updated>2004-12-20T11:30:55Z</updated>
<author>
<name>grant</name>
<email>grant</email>
</author>
<published>2004-12-20T11:30:55Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=17843af598da0d77ccfd28ea07f244a331890253'/>
<id>urn:sha1:17843af598da0d77ccfd28ea07f244a331890253</id>
<content type='text'>
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&gt;=5.8.5nb5 so the correct
dependencies are registered and the binary packages are distinct.

addresses PR pkg/28619 from H. Todd Fujinaka.
</content>
</entry>
<entry>
<title>Initial addition of p5-Module-Signature version 0.41 in the NetBSD Packages</title>
<updated>2004-11-11T18:11:58Z</updated>
<author>
<name>seb</name>
<email>seb</email>
</author>
<published>2004-11-11T18:11:58Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=ecd8ab2fcd9f6128e86c6a8ba3e427ca51ac3403'/>
<id>urn:sha1:ecd8ab2fcd9f6128e86c6a8ba3e427ca51ac3403</id>
<content type='text'>
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.
</content>
</entry>
</feed>
