Bill Allombert <bill.allomb...@math.u-bordeaux1.fr> writes: > On Thu, Mar 04, 2010 at 11:00:45PM +0100, Stefano Zacchiroli wrote:
>> Currently, packages ships file checksums which are computed at package >> build time by the means of dh_md5sums (usually), and stored under >> /var/lib/dpkg/info/*md5sums. Several people find those checksums >> useful, mostly for file corruption detection a-la CRC. >> Empirical tests show that the archive coverage is pretty good, most >> packages seem to ship those checksums. >> Hence, there is a desire to turn a similar feature into, for start, a >> SHOULD requirement, meant to become a MUST later on. > If we are moving that way, maybe it would make sense for the checksums > to be generated by dpkg-buildpackage. One does have to be able to exclude some things on a per-package basis since there are some weird cases in the archives. (Files in /var/lib/[ai]spell are the one case that Lintian knows about at present.) -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874okulift....@windlord.stanford.edu
