Date: Thu, 26 Apr 2007 10:53:14 -0400 From: Bill Moran <wmoran@potentialtech.com> To: Vivek Khera <vivek@khera.org> Cc: ports@freebsd.org Subject: Re: Making a local branch of the ports tree Message-ID: <20070426105314.7dd55052.wmoran@potentialtech.com> In-Reply-To: <4FEBCC0A-FBF5-4A30-83D0-EFF0B60450CA@khera.org> References: <20070425132239.64ebbb14.wmoran@potentialtech.com> <4FEBCC0A-FBF5-4A30-83D0-EFF0B60450CA@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to Vivek Khera <vivek@khera.org>: > > On Apr 25, 2007, at 1:22 PM, Bill Moran wrote: > > > My thought is to make /usr/ports/private (or similar) and teach cvsup > > not to blow it away. Then I just need to make sure that portupgrade > > and other tools see it. > > > > Does anyone have a HOWTO or list of steps to get this going? I know > > this has been discussed before but I can't find any reference to it > > now. > > I use /usr/port/local and name all the ports "kci-XXX" for whatever > port we have. mostly these are pseudo ports which pull in all the > dependencies for our various server needs. (I'll probably post this > to my website sometime...) Wow, that's pretty damn detailed. If you have trouble getting it ready for web publication, let me know and I'll maybe jump in and help out. This is great stuff. [snip] -- Bill Moran http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070426105314.7dd55052.wmoran>