Date: Tue, 3 Apr 2007 20:27:53 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: pav@FreeBSD.org Cc: ports@FreeBSD.org, Dan Casey <dcasey@debtresolve.com> Subject: Re: Ports tree infrastructure Message-ID: <20070403202753.6e1151a7@Magellan.Leidinger.net> In-Reply-To: <1175619865.57512.1.camel@ikaros.oook.cz> References: <461275DC.20408@debtresolve.com> <1175619865.57512.1.camel@ikaros.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Pav Lucistnik <pav@FreeBSD.org> (Tue, 03 Apr 2007 19:04:25 +0200): > Dan Casey p=C3=AD=C5=A1e v =C3=BAt 03. 04. 2007 v 11:42 -0400: >=20 > > I am setting up a single server as a 'build box' for our freebsd > > servers. We want to build our own packages because > > 1. we may need to compile certain ports with different flags then > > freebsd chooses. > > 2. We want to update ports only when needed. Ie: Unless we need > > something in a new version of a port, or unless there is a security > > hole, we want to keep the old version. >=20 > http://tinderbox.marcuscom.com/ ? >=20 > > When I want to upgrade a port, I would copy it over from the current > > ports tree. >=20 > This will not work. You need to have a consistent ports tree. Just > pulling a single new port and inserting it into old tree will not work. Sounds a little bit harsh... I would say "It may or may not work. If it doesn't work don't complain here." as this will work if it is done right. But doing it right (handling the dependencies and the ports infrastructure bits) requires time/man power/following the commits. Bye, Alexander. --=20 http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070403202753.6e1151a7>