From owner-freebsd-ports@FreeBSD.ORG Thu Sep 18 19:28:00 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 CDCDF16A4B3 for ; Thu, 18 Sep 2003 19:28:00 -0700 (PDT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CC6743FCB for ; Thu, 18 Sep 2003 19:27:59 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.9/8.12.8) with ESMTP id h8J2RIUC093947; Fri, 19 Sep 2003 11:57:19 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "M. Warner Losh" , paul@freebsd-services.com Date: Fri, 19 Sep 2003 11:57:18 +0930 User-Agent: KMail/1.5.3 References: <1063802358.33631.44.camel@localhost> <20030918.201059.44982857.imp@bsdimp.com> In-Reply-To: <20030918.201059.44982857.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309191157.18409.doconnor@gsoft.com.au> X-Spam-Score: -3.7 () CARRIAGE_RETURNS,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_03_05,TO_BE_REMOVED_REPLY,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: ports@freebsd.org Subject: Re: Base packaging 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: Fri, 19 Sep 2003 02:28:00 -0000 On Friday 19 September 2003 11:40, M. Warner Losh wrote: > P.S. How do you handle the packlist generation? The ports system > doesn't automatically generate these things, as far as I can tell, and > I didn't see anything that you've added to do this. > > My agenda, if you will, on this is to deal with: > > upgrades: portupgrade can grok packages. If you had a good way to > generate the package list, then we could make it a lot easier to do > binary upgrades. Thie would let me have a big meta-port that > covers all the 'standard' things on the machine, including the os. > Chances are good that some care would need to be taken in > portupgrade to make sure that it doesn't use binaries in place that > will be replaced. I have a tool that generated plists (mostly). It uses ktrace/kdump to find out what files are touched. It's a bit primitive and slow, but it does work :) > subsetting: with the proper set of subsetting, one could easily > create packages such that they could install just what they > needed. It might be good to have a few like "minimal to boot with > rc.d" and the like. > > nopriv: it should be possible to build a release w/o any privs at > all. NetBSD does this with hacks to install and pax to journal > installation stuff in a certain mode and a new mkfs program to take > that info and create a file system image that can be used in the > target environment. > > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5