From owner-freebsd-current@FreeBSD.ORG Tue May 6 19:53:13 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B6EF37B401 for ; Tue, 6 May 2003 19:53:13 -0700 (PDT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B02DE43FAF for ; Tue, 6 May 2003 19:53:12 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.12.9/8.12.9) with ESMTP id h472rAPx011697; Tue, 6 May 2003 22:53:11 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200305070126.h471QjNr067902@khavrinen.lcs.mit.edu> References: <3EB8109D.2060307@isi.edu> <20030507083913.Y18014@gamplex.bde.org> <200305070126.h471QjNr067902@khavrinen.lcs.mit.edu> Date: Tue, 6 May 2003 22:53:10 -0400 To: Garrett Wollman From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.28 cc: current@freebsd.org Subject: Re: hardcoded -C argument to ${INSTALL} X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2003 02:53:13 -0000 At 9:26 PM -0400 5/6/03, Garrett Wollman wrote: >< said: > >> I think this "remove stale pieces" issue is one that we have >> to find a decent solution to, because it keeps popping up >> every few months (in slightly different contexts), and it's >> going to drive us all nuts. > >...which is odd because releases have come with mtree files for >quite a few years now, and they contain all the information >necessary to compute the set difference between two arbitrary >releases. It wouldn't take too much programming to add a flag >to mtree(8) which implements ... That's kind of where I was heading with one of the solutions I tried to implement, but I am pretty much ignorant of the mtree files. Do they really contain a list of all files? I thought it was just a directory list. Also, would this work for people tracking -stable or -current on a periodic basis? Ie, are the files up-to-date for every buildworld, or are they only complete and correct at release points? Do the mtree files reflect options the administrator has set when doing a buildworld, things like NO_KERBEROS or NO_PERL or NO_GAMES, etc, etc? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu