On Thu, 30 May 2002, Greg Wooledge wrote: > The normal policy (with most other projects) is that CVS should not have > configure in it, but nightly tarballs extracted from CVS should have it. > Anyone following CVS is expected to have all the tools necessary to > contribute as a developer; people compiling snapshots have lesser > requirements.
This is my point as well. In general, no files that are automatically generated should by in a CVS. These files can be generated according to their dependencies by make.. For example, the patch sent earlier contained modifications in configure.in, and also a lot of stuff from configure, which is built from configure.in. Actually, most of the patch was on changes to configure itself, which is quite redundant. Also, configure will be different on each developer's system as people might use slightly different versions of autoconf. The effect will be (hopefully) the same, but the file itself will be different. As a result, one will end up with files in his local CVS directory that differ from the CVS repository, even though this difference is irrelevant, as these files are generated based on other files. > I'm not sure whether the LAME developers have a formal policy on this > issue or not. Me neither. And of course this is just a suggestion, it might be useful to lame developers. Then again, it might be not :) Anyway, as a sample one might consider looking at the CVS of Ogg Vorbis. There you have a script called autogen.sh, which runs all the autoconf / automake / etc. stuff to set up the configuration / make environment. But this is just an example, I've seen this pattern widely used. Akos _______________________________________________ mp3encoder mailing list [EMAIL PROTECTED] http://minnie.tuhs.org/mailman/listinfo/mp3encoder
