From owner-freebsd-arch@FreeBSD.ORG Tue Jun 26 16:24:22 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 E11BE106566C for ; Tue, 26 Jun 2012 16:24:22 +0000 (UTC) (envelope-from sjg@juniper.net) Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by mx1.freebsd.org (Postfix) with ESMTP id 7A4E58FC0C for ; Tue, 26 Jun 2012 16:24:20 +0000 (UTC) Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKT+niNCcfM9EH1664cDx176wz7ZbmJ+ae@postini.com; Tue, 26 Jun 2012 09:24:22 PDT Received: from magenta.juniper.net (172.17.27.123) by P-EMHUB03-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 26 Jun 2012 09:21:44 -0700 Received: from chaos.jnpr.net (chaos.jnpr.net [172.24.29.229]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id q5QGLfh50981; Tue, 26 Jun 2012 09:21:42 -0700 (PDT) (envelope-from sjg@juniper.net) Received: from chaos.jnpr.net (localhost [127.0.0.1]) by chaos.jnpr.net (Postfix) with ESMTP id 8CE5058081; Tue, 26 Jun 2012 09:21:41 -0700 (PDT) To: Eric van Gyzen In-Reply-To: <4FE9D84E.7080402@vangyzen.net> References: <20120626063017.D05DA58081@chaos.jnpr.net> <86wr2uwdgf.fsf@ds4.des.no> <4FE9D84E.7080402@vangyzen.net> Comments: In-reply-to: Eric van Gyzen message dated "Tue, 26 Jun 2012 10:42:06 -0500." From: "Simon J. Gerraty" X-Mailer: MH-E 7.82+cvs; nmh 1.3; GNU Emacs 22.3.1 Date: Tue, 26 Jun 2012 09:21:41 -0700 Message-ID: <20120626162141.8CE5058081@chaos.jnpr.net> MIME-Version: 1.0 Content-Type: text/plain Cc: Tim Kientzle , freebsd-arch@freebsd.org, sjg@juniper.net, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= 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 16:24:23 -0000 On Tue, 26 Jun 2012 10:42:06 -0500, Eric van Gyzen writes: >Tim's idea sounds great, and would cover several use-cases. >Specifically, it leaves the build artifacts in the usual places so >other, later builds can build against them, whereas writing the Yes, this is almost exactly what we are planning to do. >artifacts directly to a tar file does not. Building a manifest would >also be very handy, and even necessary for correct packaging of the >artifacts from an unprivileged build, where the on-disk meta data are >not "correct". Exactly. >I'm already doing something like this at $WORK, but not using >buildworld/installworld (to my dismay). I manually maintain an mtree FWIW we don't plan to use buildworld either ;-) But until we can offer a useful alternative, incremental improvements can be helpful. >file which gets fed to makefs to build an mfsroot. Although I like the >fascist control of this method, it's more work to maintain. Automation >is good. We've been using essentially this method for many years (10+), but using a hacked version of mkisofs - for freebsd we are re-doing it for makefs. The maintenance isn't that big a deal - and yes automation wins. --sjg