On 31 Mai, Toby Speight wrote:
>>> Although ./configure is a generated file, it shouldn't change from
>>> host to host - and I don't think it's reasonable to require every
>>> developer to have the right version of autoconf, so it should be in
>>> CVS.
>
> Greg> The normal policy (with most other projects) is that CVS should
> Greg> not have configure in it, but nightly tarballs extracted from
> Greg> CVS should have it.
>
> That makes sense. It shouldn't be necessary to have autoconf merely
> to build the latest snapshot, but it's reasonable to expect developers
> to do so.
I've just updated autoconf from 2.13 to 2.5x recently. Now configure.in
uses different keywords, so the autoconf versions are not compatible.
I've also seen this incompatibility earlier. So the intend of having
generated files in the CVS is:
- don't force developers to have auto* if they want to help in the
development of LAME (why should I install auto* if I just want to
modify *.[ch]?)
- don't force developers to use particular auto* versions if they don't
have to modify the auto* input files
- make it easier for non-developers to test the recent LAME development
(you just have to learn how to "cvs co" LAME and you can test it)
- provide a consistent development environment (as far as auto*
reaches)
Bye,
Alexander.
--
0 and 1. Now what could be so hard about that?
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
