Date: Tue, 28 Mar 2006 19:30:48 -0600 From: "Douglas K. Rand" <rand@meridian-enviro.com> To: Shaun Amott <shaun@inerd.com>, freebsd-ports@FreeBSD.org Subject: Re: Local Patch Hierarchy Message-ID: <87vetyavg7.wl%rand@meridian-enviro.com> In-Reply-To: <20060329000808.GA1206@picobyte.net> References: <87r74qm1xy.wl%rand@meridian-enviro.com> <20060329000808.GA1206@picobyte.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug> First off, I was wondering if there is a method that I just Doug> missed that will already accomplish this, or something near Doug> this. And if not, does anybody think it is a good idea. Shaun> Well, you can put your local patches inside the 'files' Shaun> directory of individual ports, and bsd.port.mk will apply them Shaun> along with the other patches. If you use cvsup to update your Shaun> ports, the additional patches won't be touched when you update. It would seem that I needed to read the cvsup manpage more closely than I did. I had always assumed that the "delete" keyword would delete any extraneous files, but clearly it doesn't: manual> In general, CVSup deletes only files which are known to the manual> server. Extra files present in the client's tree are left manual> alone, even in exact mode. Shaun> I think this is generally the accepted way of doing what you Shaun> want. And if I pick decent names for my local patches they won't conflict with future patches and will be applied in a predictable manner. Thanks for the tip.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87vetyavg7.wl%rand>