>>>>> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> On Fri, 11 Feb 2000, Allan Rae wrote:
>> You're a developer! You have autoconf and automake installed why
>> not libtool as well? I think Lars has been been spoiling you.
>>
>> Why do we need libtool in the repository? Sure it's got to be
>> included in the dist but it doesn't need to be in the repository
>> for that to happen.
Hmm, I message that I did not get... Did this one find its way in the
mailing list?
Concerning libtool. I just found out that my poblem is that I _do_
have libtool installed on our network, but it is version 1.3.2. So
I'll have to have it installed just for this release.
Allan> While I'm on the subject while is acinclude.m4 in the
Allan> repository? We build it with autogen.sh and noone should be
Allan> editting it anyway. Is this just that someone forgot to do a:
Allan> cvs rm acinclude?
We could remove it if it was generated automatically in makefile, like
configure or config.h.in.
Allan> It'd be one less file to give irrelevent conflicts on.
Allan> Irrelevent in the sense that I hadn't modified it locally but
Allan> cvs still says there are conflicts -- just like in 89 other
Allan> files only 8 of which were relevent!
Maybe finding out why cvs assumes there are conflicts would be more
productive than removing as many files as possible...
Allan> As you can probably guess I'm merging the latest HEAD into my
Allan> branch. Why is it that: cvs update -j sigc-3 -j HEAD
Allan> removes all the new files I had in my branch? It's supposed to
Allan> be merging the differences not just replacing everything with
Allan> HEAD which is exactly what it did do! I'm sure I never had
Allan> these problems when I was doing the sgi-stl stuff and used
Allan> exactly the same form of the update command.
Don't know about that...
JMarc
