Vick Khera <vivek at khera.org> writes:
> 2010/10/13 Christopher Browne <cbbrowne at ca.afilias.info>:
>>> Now we have 2 different tarballs around having different md5sums, or
>>> so...
>>
>> I'm not thrilled with that, but our process of generating the md5sums is
>> pretty "open"; it's literally a make target.
>>
>
> Well, it plays more to the package building processes, like FreeBSD
> ports. When it downloads a tar file, it compares the known SHA256
> (and/or MD5 and/or SHA1) checksum to make sure the file is what was
> expected.  At this point, the checksums for FreeBSD ports have the new
> file, so I'm kinda leaning towards not renaming anything, but I don't
> know the effects to others.

Ah, so BSD ports actually captures the checksum, and uses it.  That's
good to know.  I'm glad that it is being used, and I suppose we ought to
document the dependency.
-- 
"cbbrowne","@","afilias.info"
Christopher Browne
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"