Date: Thu, 24 Apr 2003 11:52:51 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: "."@babolo.ru Cc: freebsd-ports@freebsd.org Subject: Re: Building ports in a chrooted tree Message-ID: <20030424115251.0e9ac845.Alexander@Leidinger.net> In-Reply-To: <1051176441.694113.643.nullmailer@cicuta.babolo.ru> References: <20030424095705.094d5ee6.Alexander@Leidinger.net> <1051176441.694113.643.nullmailer@cicuta.babolo.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 24 Apr 2003 13:27:21 +0400 (MSD)
.@babolo.ru wrote:
> > Build a port in the chroot, at the same time build the same port in
> > /usr/ports. This is the problem I don't want to have.
> Yes.
> I use one /usr/ports for tens of hosts and
> hundreds jail.
> Just let not write to /usr/ports anything
> when build ports and you have no interaction.
> cat /etc/make.conf
> ..
> PACKAGES=${TMPDIR}
> WRKDIRPREFIX=${TMPDIR}
> MAKEOBJDIRPREFIX?=${TMPDIR}
I know about those variables and use some of them myself in some
environments.
> ..
> where TMPDIR is out of /usr/ports (and /usr/src)
> And mount /usr/ports read only in jails
> (and most hosts)
You describe a solution for a problem I don't want/have to solve. The
SystemOnCD port is supposed to appear in the ports collection, and it
should be buildable without any modification anywhere. And at the same
time I want to allow the build of other ports on the build system
without getting problems in the SystemOnCD-chroot.
Bye,
Alexander.
--
Intel: where Quality is job number 0.9998782345!
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030424115251.0e9ac845.Alexander>