Date: Wed, 14 Mar 2007 02:12:58 -0500 From: "Scot Hetzel" <swhetzel@gmail.com> To: "Nate Eldredge" <nge@cs.hmc.edu> Cc: freebsd-ports@freebsd.org Subject: Re: portsnap and local patches Message-ID: <790a9fff0703140012o7a034644vc631e07dce2e073e@mail.gmail.com> In-Reply-To: <Pine.LNX.4.64.0703132319320.1824@knuth.cs.hmc.edu> References: <Pine.LNX.4.64.0703132319320.1824@knuth.cs.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0703140012o7a034644vc631e07dce2e073e>