[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Re: Identical dices in GNU

From: Joern Thyssen
Subject: Re: [Bug-gnubg] Re: Identical dices in GNU
Date: Mon, 7 Jul 2003 09:51:12 +0000
User-agent: Mutt/1.4.1i

On Mon, Jul 07, 2003 at 11:38:03AM +0200, Olivier Baur wrote

> PS: BTW, when I commited the changes, here the output I got from cvs:
> Checking in Makefile.in;
> /cvsroot/gnubg/gnubg/Makefile.in,v  <--  Makefile.in
> new revision: 1.115; previous revision: 1.114
> done
> Checking in configure;
> /cvsroot/gnubg/gnubg/configure,v  <--  configure
> new revision: 1.98; previous revision: 1.97
> done
> Checking in rollout.c;
> /cvsroot/gnubg/gnubg/rollout.c,v  <--  rollout.c
> new revision: 1.106; previous revision: 1.105
> done
> How come Makefile.in and configure are committed to the CVS too, as 
> they are created during the build process?

They're commited for the convinience of users who do not have autoconf
and automake. Also, the tarballs on alpha.gnu.org will be ready to
"./configure; gmake". 

I usually always do "cvs ci <only-the-files-I've-modified>" to avoid
commiting all the "extra" files. Otherwise Makefile.in etc will be
committed a gazillion times because their content will vary with
different versions of automake/autoconf.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]