From owner-freebsd-arch@FreeBSD.ORG Tue Jun 26 15:18:17 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 756C81065743 for ; Tue, 26 Jun 2012 15:18:17 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 4ECE98FC08 for ; Tue, 26 Jun 2012 15:18:17 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q5QFI8bT035758; Tue, 26 Jun 2012 15:18:08 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id 7ftgu7422dyda4pqhnysb26f2n; Tue, 26 Jun 2012 15:18:08 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Tim Kientzle In-Reply-To: <86wr2uwdgf.fsf@ds4.des.no> Date: Tue, 26 Jun 2012 08:18:05 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120626063017.D05DA58081@chaos.jnpr.net> <86wr2uwdgf.fsf@ds4.des.no> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= X-Mailer: Apple Mail (2.1278) Cc: freebsd-arch@freebsd.org, Simon Gerraty Subject: Re: Allow user install X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 15:18:17 -0000 On Jun 26, 2012, at 3:54 AM, Dag-Erling Sm=F8rgrav wrote: > Simon Gerraty writes: >> The patch below is a step towards supporting unprivileged buildworld >> etc. Eg. >=20 > Wow, this is really cool - and long overdue. >=20 > I've been thinking for a while that some bor^H^H^Henterprising soul > should hack install(1) so that if a specific environment variable is > set, it writes the file to a tarball instead of writing it to disk. > Unfortunately, there would still be a ton of ${LN} etc. that would = need > to be handled somehow. Better idea: have the build write a textual description of the tar entries. That description can then be fed to tar to build the actual tarball. The description format that tar already supports is a variant mtree format borrowed from NetBSD. Each line specifies the tar entry fields (filename, owner, permissions, etc) and the filename where the file contents are stored. Tim