Date: Mon, 6 Mar 2006 09:06:00 +0200 From: Vasil Dimov <vd@FreeBSD.org> To: Jeremy Messenger <mezz7@cox.net> Cc: ports@freebsd.org, Vivek Khera <vivek@khera.org> Subject: Re: best practices for private ports? Message-ID: <20060306070600.GA70987@qlovarnika.bg.datamax> In-Reply-To: <op.s5stvko79aq2h7@mezz.mezzweb.com> References: <D61146D9-35C1-47BA-85C7-C954D930F832@khera.org> <op.s5stvko79aq2h7@mezz.mezzweb.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 02, 2006 at 12:34:22PM -0600, Jeremy Messenger wrote: > On Thu, 02 Mar 2006 09:24:48 -0600, Vivek Khera <vivek@khera.org> wrote: >=20 > >I have a few meta-ports I use to configure my base systems. eg, I have = =20 > >a "kci-dbserver" port that just has runtime requirements for postgres, = =20 > >slony, mysql, and nullmailer. > > > >Right now I made a subdirectory in ports called local to put them in, = =20 > >but portsnap likes to delete it regularly :-( These are very specific = =20 > >to my server configurations so don't really make sense for inclusion in = =20 > >the main ports tree. > > > >What is the preferred location/mechanism for having local ports? =20 > >Ideally I'd like it to integrate with portupgrade which looks only in = =20 > >/usr/ports/* for the port files. >=20 > Use CVSup instead portsnap or copy marcusmerge.sh[1] with some tweak or = =20 > write your own script something similar to marcusmerge.sh that fit your = =20 > need. That's all I can think of. >=20 > [1] http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi/portstools/ >=20 > Cheers, > Mezz >=20 >=20 Or create a script that calls portsnap and then restores your "local" ports automatically, something like cp -r /usr/ports-local/category/port /usr/ports/category/ Btw, have you tried playing with /usr/ports/.cvsignore? Good luck! --=20 Vasil Dimov --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFEC99YFw6SP/bBpCARAnvzAKDChKZHmVifwO51ADi79ufnoJW9aACfeuZp HB+yS9XYj1JUmCUK4RQrNRI= =Wyj5 -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060306070600.GA70987>