In response to Vivek Khera <[EMAIL PROTECTED]>: > > 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 _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
