[GRASS5] Thought on my CVS problem

Bernhard Reiter bernhard at intevation.de
Fri Sep 15 04:07:54 EDT 2000


On Wed, Sep 13, 2000 at 07:06:05PM +1100, James Cameron wrote:
> On Wed, Sep 13, 2000 at 08:58:39AM +0200, Bernhard Reiter wrote:
> > On Wed, Sep 13, 2000 at 08:26:02AM +1100, James Cameron wrote:

> > Not everybody has a recent autoconf or flex/bison installed and properly
> > configured. Which means we are excluding some people from using the
> > CVS directly. (I do not think it is a problem, but it should be noted.)
> 
> I will politely continue to disagree.
> 
> Those people can go get a recent autoconf or flex/bison installed, if
> they are wanting to compile the sources.  

They could, but if it is unnecessary it is an unnecessary hassle.
(And it can be quite a pain getting autoconf flex and bison installed.)

> Some of the build utilities
> may have architecture dependencies that render their output wrong for
> the platform the end user of a tarball tries to compile on.

But not configure, flex and bison.

> Example: assume you use a Linux Intel machine to build the flex/bison
> output, and further assume that flex/bison generates 32-bit specific
> code on your machine.  It gets committed to CVS or saved in the tarball,
> and then I install it on my Linux Alpha machine.  I blindly try to
> build and the 32-bit code is used on my 64-bit machine, causing
> problems.  I end up writing lots of mail, and eventually someone says
> "oh, try deleting the source files generates by flex or bison".
> 
> Doesn't seem right, somehow.

True, bugt AFAIK the assumption is wrong.
The generated configure script and flex and bison code _should_
be platform independant. If it is not, the right way would be to fix
them.

> Most other open source packages require that I have the tools to build
> them.
> 
> > > Further, the files named should be included in a .cvsignore file in
> > > the directory that they will reside, and the .cvsignore files should be
> > > in CVS.
> > This only helps with imports, right?
> 
> No, it also helps with commit and diff, the files listed in .cvsignore
> don't get listed with a question mark beside them.  

Actually I think that this question mark helps clarify the situation
of the files. The actual behaviour of CVS is the same in this case.

> You should be able
> to do a "make distclean" before a "cvs diff" and see no extra files 
> mentioned.  

True, because they are not there, if they do not belong in CVS: :)

> Good test of the coverage of .cvsignore.  It also helps to make sure
> that you have all the source files properly added to CVS.

	Bernhard
-- 
Professional Service around Free Software                (intevation.net)  
The FreeGIS Project				            (freegis.org)
Association for a Free Informational Infrastructure            (ffii.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 236 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20000915/7e6b9569/attachment.bin


More information about the grass-dev mailing list