Date: Wed, 11 Jun 2014 14:09:50 -0700 From: Anton Afanasyev <aasoft@gmail.com> To: paul+usenet@w6yx.stanford.edu Cc: ports list <freebsd-ports@freebsd.org> Subject: Re: poudriere and local patches to ports Message-ID: <CAEAhP2jYwFqQOVn0AQCRgBiX_ff9Qn5OnDeS0ORYeUnHEwXwrQ@mail.gmail.com> In-Reply-To: <lna5ng$j69$1@usenet.ziemba.us> References: <5C78F5B6-643F-4ABA-9FC2-CBED9C6C56B2@langille.org> <lna5ng$j69$1@usenet.ziemba.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 11, 2014 at 11:04 AM, G. Paul Ziemba <pz-freebsd-ports@ziemba.us > wrote: > Disclaimer: I set up my poudriere environment almost a year ago, > so there could be new poudriere features to address this issue > that I'm not aware of. > NOTE: I have not tested the method I describe, but I've exercised this idea mentally for a while. If you do end up taking this approach, I would appreciate it if you let me know how it worked out for you. Poudriere supports updating its ports tree via alternative methods, namely git and svn. You could thus set up a clone of FreeBSD's ports repository that gets refreshed periodically (a simple script) and to which you would also commit your own patches. This also has the added benefit of making the history of all your patches' changes easily available. Anton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEAhP2jYwFqQOVn0AQCRgBiX_ff9Qn5OnDeS0ORYeUnHEwXwrQ>