It is generally a good idea not to put generated files like this in CVS.
CVS is really meant for developers, who could be expected to have the
build tools installed on their system.
If you want to build stuff from cvs (this applies to just about everything
in the gnome cvs tree), it is a good idea to have up to date build tools.
Note that these packages are not required if building from tarballs.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On 17 Oct 1999, Daniel Wang wrote:
>
> Brian Jepson <[EMAIL PROTECTED]> writes:
>
> > On Mon, 18 Oct 1999, James Henstridge wrote:
> >
> > > One other person had a problem like this. It turned out that he had
> > > automake-1.3 rather than 1.4. If you have an old automake, then this
> > > would be your problem.
> >
> > Thank you - that appears to be the problem - I have automake 1.3-2 from
> > the Debian 2.1 distribution. I'll get a newer version and try it out.
>
> Is there any reason not to check in the configure script itself into the CVS
> repository?
>
> I know it's a derived file and really shouldn't be checked in, but I think
> it would solve a lot of these versioning issues, and make it easier for
> random people to just suck sources from the repository type configure and
> build..
>
