On Fri, Aug 31, 2001 at 09:16:15PM -0700, Ryan Bloom wrote:
> On Friday 31 August 2001 19:31, William A. Rowe, Jr. wrote:
> > From: "Greg Stein" <[EMAIL PROTECTED]>
> > Sent: Friday, August 31, 2001 9:30 PM
> >
> > > On Fri, Aug 31, 2001 at 03:02:32PM -0700, Ryan Bloom wrote:
> > > >...
> > > > exports.c shouldn't be cleaned, correct, because it is a part of the
> > > > distribution, or at least it should be if it isn't already.
> > > > config.nice is not a part of the distribution however, and should be
> > > > removed by make distclean.
> > >
> > > -1 on *any* form of clean that tosses config.nice
> > >
> > > That holds *my* information about how I repeatedly configure Apache. That
> > > is a file that I use, and is outside of the scope of the
> > > config/build/whatever processes. Its entire existence is to retain the
> > > information. Cleaning it is not right.
> >
> > What are you talking about? We are talking about cleaning for packaging to
> > _other_ computers, not yours. That's what rbb is speaking of by
> > 'distclean', clean enough for redistribution.
>
> Exactly. The whole point and definition of make distclean, is that it cleans
> things to the point that it could be redistributed to another machine. If you
> are just trying to clean the directory, then make clean is what you want. If
> make clean doesn't remove enough for you, then something else is wrong.
I use distclean on my computer all the time. Along with extraclean. Neither
of those targets should toss config.nice. *That* is what I mean.
To be clear: nothing in our build/config/whatever should remove config.nice
"Clean" rules are about cleaning out state that might affect a build in some
way. So we toss object files, generate makefiles, the configure script,
whatever. But config.nice doesn't fall into that camp because it is not a
"stateful" file. It is for the user to rebuild what they had before.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
