On Wednesday 14 March 2007 02:12, Scot Hetzel wrote: > On 3/14/07, Nate Eldredge <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > portsnap is a very nice way to keep your ports tree in sync, but > > it has the disadvantage that it keeps your ports tree in sync :) > > If you make local changes (e.g. adding a patch) they get > > clobbered. Does anyone know of a convenient way to keep ports up > > to date while preserving local patches? > > One way to keep your local changes is to use cvs to checkout and > update the ports tree, you then make your modifications to the > port. > > You will need to fix any conflicts manually between an updated port > and your changes. > > Scot
csup/cvsup has the nice feature of not touching files that shouldn't be there, so my solution to that problem is to create a new directory for my local changes, which csup/cvsup will nicely ignore. -- Thanks, Josh Paetzel _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
