Date: Thu, 02 Mar 2006 12:34:22 -0600 From: "Jeremy Messenger" <mezz7@cox.net> To: "Vivek Khera" <vivek@khera.org> Cc: ports@freebsd.org Subject: Re: best practices for private ports? Message-ID: <op.s5stvko79aq2h7@mezz.mezzweb.com> In-Reply-To: <D61146D9-35C1-47BA-85C7-C954D930F832@khera.org> References: <D61146D9-35C1-47BA-85C7-C954D930F832@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 02 Mar 2006 09:24:48 -0600, Vivek Khera <vivek@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[1] with some tweak or write your own script something similar to marcusmerge.sh that fit your need. That's all I can think of. [1] http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/portstools/ Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.s5stvko79aq2h7>