Re: FYI: update .info files in $(srcdir) again

[Alexandre Duret-Lutz]

>>> "Tom" == Tom Tromey <address@hidden> writes:

 >>>>>> "adl" == Alexandre Duret-Lutz <address@hidden> writes:
 >>>>> "ttn" == Thien-Thi Nguyen <address@hidden> writes:

 ttn> drat, i really came to appreciate .info files in the build tree.

 adl> I'm interested to know why.  I've only heard about arguments
 adl> against this so far.

 Tom> Most projects don't check in their .info files.  In fact, I don't know
 Tom> of any that do.  However, for these projects it is still useful to
 Tom> allow the source tree to be made read-only.

How would you call this option?

I confess I'm not really fond of
adding/testing/documenting/maintaining yet another option, especially
because it will produce unportable Makefiles.

As long as there is a possibility to have .info files in both
the build tree and the source tree (this happens for instance
when you attempt a VPATH build from a distributed tarball that
already include the .info files) we cannot write portable rules.
AFAICT the only way to be portable is to either build is the
source tree (as the GCS says), or don't distribute the .info
files (Karl & Ralf case).

[...]

-- 
Alexandre Duret-Lutz