On 21 May 2008, at 04:53, Daniel Macks wrote: > Could this pile of sed patchscript be converted into an actual .patch > file? Feel free ! pkg belongs to "None" ... > That way one doesn't have to learn sed (and install fink's sed!) > to understand what's happening here. As a bonus, if the source changes > in future versions, either the patch will continue to work or it will > fail loudly, whereas a script full of regexp- or line-number-based > changes may simply and silently do "something different".
Understand your arguments _ on the other hand a patch file tends to be much more verbose, and more difficult to edit. Further a patchscript allows to group related items, even when those (sed or other) commands affect a large number of files, and to comment such items individually if needed.. Hence my preference for patchscripts in general ... :) Jean-Francois ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-users
