Frank Küster wrote: > There are also other alternatives to dpatch; one is Debian-specific and > i keep forgetting its name, and there's quilt. The main advantage of > quilt IMHO is that it doesn't duplicate the whole tree when editing and > updating the patch, which can be time- and disk-consuming in large > projects. Instead it keeps a list of files for the patch one is editing > and only keeps copies of these.
Out of curiosity, does quilt have a mechanism similar to dpatch that allows you to treat shell scripts as "patches"? My inability to find such a feature was the main reason I opted for dpatch over quilt in the Cernlib package -- I needed to move a bunch of files around within the source, and doing so with a pure patch system will result in huge and fragile diff files (two copies of each file to be moved, which breaks if upstream changes any of them!). But now it sounds like I'm missing out on some features by not using quilt. regards, -- Kevin B. McCarty <[EMAIL PROTECTED]> Physics Department WWW: http://www.princeton.edu/~kmccarty/ Princeton University GPG: public key ID 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
