brooks at freebsd.org
Wed Apr 11 03:27:33 UTC 2007
On Tue, Apr 10, 2007 at 09:15:04PM -0500, Josh Paetzel wrote:
> Vulpes Velox wrote:
> > I was just wondering what any one else thought of the idea of adding
> > a local directory to the ports tree and to the .cvsignore. This would
> > be a directory for users to put local custom ports.
> There's nothing to stop you from creating /usr/ports/local right now
> and just using it. You don't need a .cvsignore if you are using
> cvsup/csup, they ignore files that aren't in the cvs repo anyways.
> Of course if you are using portsnap that might be a different story,
> not sure how it handles updates...
Just fine. The author even added the -l option at my request so you can
still use portsnap's INDEX updating stuff. You just need to collect
the results of "make describe" in your local ports and pass the file
containing it as the argument to -l when updating. I'm using it at work
with a wrapper script that updates my local ports via subversion and
updates official ports via portsnap on one go.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20070411/32d5130a/attachment-0002.pgp
More information about the freebsd-ports