> 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.
Le Fri, Mar 05, 2010 at 05:51:33PM +0100, Bill Allombert a écrit : > > If we are moving that way, maybe it would make sense for the checksums > to be generated by dpkg-buildpackage. Hello everybody, while working on another package, I came to realise that the Policy does not describe the md5sums file at all. Would somebody be interested to submit a patch ? Have a nice Sunday, -- Charles Plessy Tsurumi, Kanagawa, Japan -- 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/20130505075021.ga27...@plessy.org
