best practices for private ports?
mezz7 at cox.net
Thu Mar 2 10:33:05 PST 2006
On Thu, 02 Mar 2006 09:24:48 -0600, Vivek Khera <vivek at khera.org> wrote:
> I have a few meta-ports I use to configure my base systems. eg, I have
> a "kci-dbserver" port that just has runtime requirements for postgres,
> slony, mysql, and nullmailer.
> Right now I made a subdirectory in ports called local to put them in,
> but portsnap likes to delete it regularly :-( These are very specific
> to my server configurations so don't really make sense for inclusion in
> the main ports tree.
> What is the preferred location/mechanism for having local ports?
> Ideally I'd like it to integrate with portupgrade which looks only in
> /usr/ports/* for the port files.
Use CVSup instead portsnap or copy marcusmerge.sh with some tweak or
write your own script something similar to marcusmerge.sh that fit your
need. That's all I can think of.
mezz7 at cox.net - mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gnome at FreeBSD.org
More information about the freebsd-ports