Ports tree infrastructure

Pav Lucistnik pav at FreeBSD.org
Tue Apr 3 17:31:38 UTC 2007

Dan Casey píše v út 03. 04. 2007 v 11:42 -0400:

> 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.

http://tinderbox.marcuscom.com/ ?

> When I want to upgrade a port, I would copy it over from the current
> ports tree.

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.

Pav Lucistnik <pav at oook.cz>
              <pav at FreeBSD.org>

Pilot to Co-Pilot: Boo.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?=
	=?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?=
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20070403/f0639ed9/attachment.pgp

More information about the freebsd-ports mailing list