At 4:13 Uhr -0700 11.05.2002, Ben Hines wrote: >At 7:07 AM -0400 5/11/02, David R. Morrison wrote: >> > Of course i suppose we'd have to update every package >> >>Not necessarily. If the Source-MD5 field is present, fink should check >>against it; if not, fink would let the download through. It then would >>be up to the maintainers of packages to add this if they wanted. > > >If we wanted to add parallel fetching using something like "puf", we >would want to have MD5 for every package so we could make sure every >download completes successfully.
In german we have a saying: "Wenn das W�rtchen 'Wenn' nich w�r, w�r das Leben halb so schwer." :-) Roughly translated: "If the word 'if', didn't exist, life would be half as hard". So you are welcome to implement the SourceMD5: / SourceNMD5: field, and submit it to the patch tracker. If the patch is well written, I will definitly accept it into the source. While automating the addition of MD5 fields would indeed be easy to script, I think at least in the first (first couple of?) versions we shouldn't require it yet in the .info file You probably will want to use the Digest::MD5 module to generate the hashes; for this it's important to code like we did for Storable-PM, that is, you must load it at run time, to prevent Fink from becoming unusable if somebody hasn't yet installed Digest::MD5. Cheers, Max -- ----------------------------------------------- Max Horn Software Developer email: <mailto:[EMAIL PROTECTED]> phone: (+49) 6151-494890 _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
