Date: Wed, 11 Jun 2003 15:04:07 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Garance A Drosihn <drosih@rpi.edu> Cc: arch@freebsd.org Subject: Re: removing stale files Message-ID: <20030611220407.GA870@athlon.pn.xcllnt.net> In-Reply-To: <p05210618bb0d4e045e1c@[128.113.24.47]> References: <20030610124747.A7560@phantom.cris.net> <20030610024524.D23396@znfgre.qbhto.arg> <20030611075750.GB57496@wantadilla.lemis.com> <20030611.093203.26943899.imp@bsdimp.com> <p05210613bb0d2187f0dd@[128.113.24.47]> <20030611190615.GA15695@dhcp01.pn.xcllnt.net> <p05210614bb0d30155a2e@[128.113.24.47]> <20030611210632.GA695@athlon.pn.xcllnt.net> <p05210618bb0d4e045e1c@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 11, 2003 at 05:33:14PM -0400, Garance A Drosihn wrote: > > > > 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 (for some definition of I :-) don't have to know. I only have to care about our (=FreeBSD) tree and I only have to come up with solutions that do not gratuitously prohibit using our (=FreeBSD) tree for unspecified purposes. Having an open mind and listen to people that use our tree in unspecified ways is generally good, but it's too much to ask of FreeBSD developers to worry about those cases. Let us worry about the common case. I'm positive we get the feedback if there's a solution that doesn't break some unknown class of environments. IMO of course. > I think at this point what we need to do is to get some > actual implementations going, and see how they work in practice. Agreed. Any KISS-able mechanism is a good start. It will get complicated all by itself :-) > 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... Yup. We can start with the locale files for example. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030611220407.GA870>