From owner-freebsd-current Tue Oct 8 9:14:53 2002 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 9A80737B401; Tue, 8 Oct 2002 09:14:52 -0700 (PDT) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02FEC43E3B; Tue, 8 Oct 2002 09:14:52 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g98GEmBY001522; Tue, 8 Oct 2002 09:14:48 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g98GEm1q001521; Tue, 8 Oct 2002 09:14:48 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 8 Oct 2002 09:14:48 -0700 From: David Schultz To: "M. Warner Losh" Cc: grog@FreeBSD.ORG, sgk@troutmask.apl.washington.edu, FreeBSD-current@FreeBSD.ORG Subject: Re: Removing old binaries Message-ID: <20021008161448.GA1414@HAL9000.homeunix.com> Mail-Followup-To: "M. Warner Losh" , grog@FreeBSD.ORG, sgk@troutmask.apl.washington.edu, FreeBSD-current@FreeBSD.ORG References: <20021007234610.GT14070@wantadilla.lemis.com> <20021008004442.GA34414@troutmask.apl.washington.edu> <20021008010442.GD57557@wantadilla.lemis.com> <20021007.191340.123335159.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021007.191340.123335159.imp@bsdimp.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake M. Warner Losh : > In message: <20021008010442.GD57557@wantadilla.lemis.com> > "Greg 'groggy' Lehey" writes: > : I think it confuses the issue rather than solving it. We're talking > : about removing binaries which are no longer needed, not replacing > : binaries that are needed. > > I'd be cool with a file that's a list of files that we had in the > system in the past, but are safe to delete. NetBSD has a list of > obsolete files, and it seems to work well there. We can just have a > set of rules for when to add to this. List all the files that have > had on a FreeBSD system since 2.0 or 3.0 to start. That's an interesting idea. If necessary, you could even make it more general by associating a script with the removal of certain components. (That ought to solve complicated problems such as the one Terry mentioned.) Utilities don't turn over too quickly, so I imagine a tool like that would be fairly easy to maintain. I disagree with Greg about making it completely automagical by default. By default, the utility should try not to do anything that the user might not expect. People who want the fully automated behavior can enable it with a few keystrokes, and if something unexpected happens at that point, it's their problem. Granted, if you're only looking for things that you *know* have been removed, as opposed to ``anything that isn't in the source tree right now'', you're less likely to step on something important. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message