On Sun, Sep 02, 2001 at 12:15:33PM -0500, William A. Rowe, Jr. wrote:
> From: "Greg Stein" <[EMAIL PROTECTED]>
> Sent: Sunday, September 02, 2001 3:22 AM
>
> > 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
>
> Then it goes into the tarball. Is that what you intend?
Don't be argumentative. Of course not. Why would a config.nice ever appear
in our tarballs? We never run "configure" in there, so it should never
appear.
> > "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.
>
> Which means it has nothing to do with cleaning the tree to a distribution
> state (or state 'ready for distribution'.)
It *does* return it to a distribution state. There is no leftover state that
could erroneously affect another configure/build process. config.nice is
outside of all that.
And "ready for distribution" is not the right semantic, nor does it apply
(as above)
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
