Complete.Org: Mailing Lists: Archives: freeciv-dev: November 2001:
[Freeciv-Dev] Re: on having to run automake
Home

[Freeciv-Dev] Re: on having to run automake

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: on having to run automake
From: Jason Dorje Short <vze2zq63@xxxxxxxxxxx>
Date: Thu, 01 Nov 2001 09:09:39 -0500
Reply-to: jdorje@xxxxxxxxxxxx

Raimar Falke wrote:
> 
> On Thu, Nov 01, 2001 at 02:10:37PM +0100, Reinier Post wrote:
> > On Fri, Oct 26, 2001 at 05:01:02AM -0700, freeciv@xxxxxxxxxxxxxxxxxxx wrote:
> > > This is an automated notification of a change to freeciv cvs,
> > > on Fri Oct 26 04:52:55 PDT 2001 = Fri Oct 26 11:52:55 2001 (GMT)
> > > by Andreas Kemnade <akemnade@xxxxxxxxxxx>
> > >
> > > ---- Files affected:
> > >
> > > freeciv/client/gui-gtk Makefile.in
> > >
> > > ---- Log message:
> > >
> > > ran automake
> >
> > Yesterday I discovered a relevant CVS feature: the CVSROOT/modules file.
> >
> > It allows you to trigger arbitrary commands upon the execution of cvs
> > commands.  So we can run automake automatically on the CVS server side.
> 
> Yes CVS has such a feature. However I think it may be overkill to
> implement such thing. How often do we add new files?

Automatically running automake has the disadvantage that if the version
of automake is changed, it may give different output and the files will
be spuriously changed.  As long as this doesn't happen, though, there is
no problem and it makes things easier and cleaner (since it will always
make the same sort of output, hopefully).

Having freeciv be automatically compiled seems like an excellent idea.

jason


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