On Mon, Jun 28, 2004 at 08:25:55PM +0200, David H. wrote: > I just noticed that this breaks a convinince for developers. Because > wheny ou update an info file _without_ adding the MD5 sum (which you > presumably do not know by then) the download loop falsely assumes you > got the wrong file. So you end up "quitting" typing fink build foo > again, soy ou get the right loop this time.
*If* I understand this all (and someone please correct me)... Now and previously, if one has a missing MD5, download gives a warning and then succeeds, and then unpacking fails. Previouosly if there was a *wrong* MD5 (for example, MD5 left over from previous version) download would succeed and then unpacking fail. Now, download itself fails in this situation. Conceptually, the whole goal here is that downloads that *appear* to work except for the fact that they fetch the wrong file should be considered a download failure. Having an incorrect MD5 in a .info is not even self- consistent, so I don't think we should allow non-failure in that case. For this scenario, commenting out the MD5 for the now-unknown file keeps the .info consistent, and allows 'fink fetch' (or the download phase of other fink modes) to succeed. dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
