Date: Wed, 14 Mar 2007 07:39:23 -0600 From: Josh Paetzel <josh@tcbug.org> To: freebsd-ports@freebsd.org Cc: Nate Eldredge <nge@cs.hmc.edu>, Scot Hetzel <swhetzel@gmail.com> Subject: Re: portsnap and local patches Message-ID: <200703140839.24188.josh@tcbug.org> In-Reply-To: <790a9fff0703140012o7a034644vc631e07dce2e073e@mail.gmail.com> References: <Pine.LNX.4.64.0703132319320.1824@knuth.cs.hmc.edu> <790a9fff0703140012o7a034644vc631e07dce2e073e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 14 March 2007 02:12, Scot Hetzel wrote: > On 3/14/07, Nate Eldredge <nge@cs.hmc.edu> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200703140839.24188.josh>