Date: Thu, 24 Apr 2003 13:27:21 +0400 (MSD) From: "."@babolo.ru To: Alexander Leidinger <Alexander@Leidinger.net> Cc: freebsd-ports@freebsd.org Subject: Re: Building ports in a chrooted tree Message-ID: <1051176441.694113.643.nullmailer@cicuta.babolo.ru> In-Reply-To: <20030424095705.094d5ee6.Alexander@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Thu, 24 Apr 2003 03:47:37 +0400 (MSD)
> .@babolo.ru wrote:
>
> > > On Wed, 23 Apr 2003 11:16:50 +0400 (MSD)
> > > .@babolo.ru wrote:
> > > > > Simplified explanation of what this does:
> > > > > This builds the world, installs it into a subdir, copies /usr/ports into
> > > > Or better nullfs mount RO it from base system
> > > > to chrooted.
> > > If I use nullfs it is possible to influence the build in the chroot by
> > > modifying /usr/ports. My goal was to be able to just start a
> > > chroot-build and forget about it, including being able to build any port
> > I too, so I use read only mounts
> > of /usr/ports
>
> 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}
..
where TMPDIR is out of /usr/ports (and /usr/src)
And mount /usr/ports read only in jails
(and most hosts)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1051176441.694113.643.nullmailer>