Sounds good to me. My primary concern was the mismatch. Being able to easily find the correct .patch for a given .info (and handle multiple concurrent versions) would be nice, but by the time I'm messing around with multple versions I could just md5 until I find the right one at a time.
dan TheSin said: : : this is much better idea. : : for devel we don't add the md5sum till we are done like the source md5 : and it solves mismatched info/patches : : On Thursday, July 10, 2003, at 12:39 PM, Kaben Nanlohy wrote: : : > Add a new optional field "Patch-MD5". If this field is present then : > refuse to use the .patch unless its md5sum matches. If the field isn't : > present then always use the provided .patch. : > : > This wouldn't help you match the .patch file to the .info file, but it : > would prevent problems like the one you encountered. -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
