On Wed, 14 Oct 2009, jesse wrote: > > > If you want to handle tarballs in vendor repositories, I see only the > > extreme solution : run md5sum on source files, and compare with a list > > just downloaded off CPAN, before compilation. > > I've been vaguely considering whether we want to ship something along > the lines of a cpan-style SIGNATURE file with each release containing a > pgp-signed list of the MD5 of every file in the distribution and a tool > to verify those signatures later on an installed system. Sounds like a somewhat natural extension to utils/perlivp.PL. I find it only somewhat useful though as it will only cover changes in Perl files and misses changes to XS code, or any of the C code in the core. Cheers, -JanThread Previous | Thread Next