From owner-freebsd-arch@FreeBSD.ORG Wed Jun 11 14:33:23 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6940337B401; Wed, 11 Jun 2003 14:33:23 -0700 (PDT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 756F043FA3; Wed, 11 Jun 2003 14:33:22 -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 h5BLXFPx028015; Wed, 11 Jun 2003 17:33:16 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20030611210632.GA695@athlon.pn.xcllnt.net> References: <20030610124747.A7560@phantom.cris.net> <20030610024524.D23396@znfgre.qbhto.arg> <20030611075750.GB57496@wantadilla.lemis.com> <20030611.093203.26943899.imp@bsdimp.com> <20030611190615.GA15695@dhcp01.pn.xcllnt.net> <20030611210632.GA695@athlon.pn.xcllnt.net> Date: Wed, 11 Jun 2003 17:33:14 -0400 To: Marcel Moolenaar From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.28 cc: grog@freebsd.org cc: ache@nagual.pp.ru cc: DougB@freebsd.org cc: "M. Warner Losh" cc: arch@freebsd.org Subject: Re: removing stale files X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 21:33:23 -0000 At 2:06 PM -0700 6/11/03, Marcel Moolenaar wrote: >On Wed, Jun 11, 2003, Garance A Drosihn wrote: > > Many suggestions amount to removing anything >> "which looks old", because "if it is old, it must be bad". > >That's not a good way to approach it. Right. That's really the main thing I want to avoid. > > That means you're removing files when you don't really know >> what they contain, or why they're there. > >Which is bad, because it means you don't know your own source >tree. No, it means that "you" (for some value of "you") do not know "my" source tree (for every value of "my", == all freebsd users). > > I'm just saying that a utility with a list of specific files is >> much less likely to blow off some poor user's foot when they >> run it. > >True. The easiest utility is a a simple for loop as the last >action of installworld, like: > >Index: Makefile.inc1 >=================================================================== >RCS file: /home/ncvs/src/Makefile.inc1,v >retrieving revision 1.365 >diff -u -r1.365 Makefile.inc1 >--- Makefile.inc1 8 Jun 2003 04:15:05 -0000 1.365 >+++ Makefile.inc1 11 Jun 2003 21:04:41 -0000 >@@ -409,6 +409,12 @@ > done > cd ${.CURDIR}; ${IMAKE} re${.TARGET:S/world$//} > rm -rf ${INSTALLTMP} >+.for F in ${STALE_FILES} >+ rm -f $F >+.endfor >+.for D in ${STALE_DIRS} >+ rmdir $D || true >+.endfor > > # > # reinstall Perhaps true, although you'll be surprised at how long that list of STALE_FILES will get... If you think this is workable, then try it. I think at this point what we need to do is to get some actual implementations going, and see how they work in practice. I'll see if I can dig up the various lists-of-files that I came up with in my earlier attempt. Well, actually, maybe I shouldn't. This does not need to be an exhaustive list. It would be fine to start with just the files we *know* will cause trouble, and go on from there. I keep trying for the perfect all-encompassing solution, and that's where I get bogged down... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu