From owner-freebsd-ports@FreeBSD.ORG Thu Apr 24 02:24:20 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E137037B401 for ; Thu, 24 Apr 2003 02:24:20 -0700 (PDT) Received: from ints.mail.pike.ru (ints.mail.pike.ru [195.9.45.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8914F43FA3 for ; Thu, 24 Apr 2003 02:24:19 -0700 (PDT) (envelope-from babolo@cicuta.babolo.ru) Received: (qmail 33698 invoked from network); 24 Apr 2003 09:42:19 -0000 Received: from babolo.ru (HELO cicuta.babolo.ru) (194.58.226.160) by ints.mail.pike.ru with SMTP; 24 Apr 2003 09:42:19 -0000 Received: (nullmailer pid 644 invoked by uid 136); Thu, 24 Apr 2003 09:27:21 -0000 X-ELM-OSV: (Our standard violations) hdr-charset=KOI8-R; no-hdr-encoding=1 In-Reply-To: <20030424095705.094d5ee6.Alexander@Leidinger.net> To: Alexander Leidinger Date: Thu, 24 Apr 2003 13:27:21 +0400 (MSD) From: "."@babolo.ru X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Message-Id: <1051176441.694113.643.nullmailer@cicuta.babolo.ru> cc: freebsd-ports@freebsd.org Subject: Re: Building ports in a chrooted tree X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2003 09:24:21 -0000 > 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)