From owner-freebsd-ports@FreeBSD.ORG Thu Sep 18 19:11:01 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 A0B4416A4B3; Thu, 18 Sep 2003 19:11:01 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 283AB43FAF; Thu, 18 Sep 2003 19:11:00 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.9/8.12.3) with ESMTP id h8J2AvTX010615; Thu, 18 Sep 2003 20:10:57 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 18 Sep 2003 20:10:59 -0600 (MDT) Message-Id: <20030918.201059.44982857.imp@bsdimp.com> To: paul@freebsd-services.com From: "M. Warner Losh" In-Reply-To: <1063802358.33631.44.camel@localhost> References: <1063802358.33631.44.camel@localhost> X-Mailer: Mew version 2.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: current@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:11:01 -0000 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. 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