Re: Beagle version / revision number issue

[Joe Shaw <joe ximian com>]

Hi,

On Wed, 2007-03-14 at 11:20 +0100, Stephan Hegel wrote:
> When starting beagled daemon I always get the following printout
> near the top of my logs:
>     ...
>     Always: Starting Beagle Daemon (version 0.2.16)
>     ...
> However, this is  not entirely true: I'm running a certain revision
> from SVN issued weeks after 0.2.16.

Generally we don't bump the version number after our releases; maybe we
should start doing that.

> Would it be possible to display the current revision number here if
> the package is fetched from SVN ? This would make life easier for
> testers as they are forced - from time to time - to switch back and
> forth between revisions to track down potential regressions.
>
> BTW, is it only the "configure.in" file where the version number is
> taken from ? Would it be ok to replace the version string , let's
> say "0.2.16" just with "r3564" ?

Assuming we can extract the revision number from somewhere in .svn (I'm
sure we can -- I just don't know how), we could probably add this.  I
don't want it to go into configure.in, though, because every time it's
touched it has to rerun the autogen.sh process.  If you don't update
very often that's not a big deal, but I try to avoid running autogen
whenever possible.

The configure.in file is the only place the version number is set.  We
then substitute it into Util/ExternalStringsHack.cs when the Util
directory is built, so we could possible substitute the revision number
in from somewhere else.

I think it can be done, but I will leave the details to you. ;)

Joe