Re: Autoconf and CVS

[Ed Hartnett]

David Fang <address@hidden> writes:

>> > Interesting thought: Wouldn't it get annoying if many devs are working
>> > on one CVS controlled project, and they have different version
>> > autotools, surely each time they commit their changes they're possibly
>> > going to have conflicts? Which would make the files unusable? (until
>> > resolved).
>>
>> Yes, this can be annoying.  As a work-around you can include some sort
>> of 'bootstrap' script so that developer's can immediately overwrite
>> the version from CVS.  Of course then changed files will be committed,
>> and there will be thrashing in CVS.  If the bootstrap script insists
>> on certain versions of the autotools, then the thrashing should go
>> away.
>
> Hi,
>
> Here's an example bootstrap/autogen.sh script that I use in my projects, I
> imagine others' may look very similar.  (With a little more sed/awk/cut
> magic, one could even *enforce* correct versions.)
>

I just use "autoreconf -i", which seems to do everything needed without me
having to remember which order to call various tools, or to maintain a
bootstrap script...

Ed
-- 
Ed Hartnett  -- address@hidden