[GRASS-dev] Re: [GRASS GIS] #587: svn versions should better reflect svn rev

GRASS GIS trac at osgeo.org
Tue Jan 12 06:37:51 EST 2010


#587: svn versions should better reflect svn rev
--------------------------+-------------------------------------------------
  Reporter:  hamish       |       Owner:  martinl  
      Type:  enhancement  |      Status:  reopened 
  Priority:  major        |   Milestone:  6.5.0    
 Component:  default      |     Version:  svn-trunk
Resolution:               |    Keywords:  g.version
  Platform:  All          |         Cpu:  All      
--------------------------+-------------------------------------------------
Changes (by hamish):

  * version:  6.4.0 RCs => svn-trunk
  * milestone:  6.4.0 => 6.5.0

Comment:

 Markus wrote:
 > What is the state in GRASS 6.4? I tried right now and get:

 This ''should'' be the revision of the latest commit to gis.h, which is
 why the -r flag says "GIS library revision number and time". This is what
 is important to qgis, core API, etc. The wx help->about window says "GIS
 Library Revision" which I'm sure will still confuse some folks in the
 absence of an over-all revision number, but none the less is fairly
 clear..


 > but indeed we are at [r40373]

 note that is moslty just interesting for dev branch builds, for a tagged
 release the exact version of the codebase that the version number refers
 to is known.

 > Perhaps we have to determine the rev version on compile time?

 which is what the `svnversion -c` added to ./configure in trunk is
 supposed to help with. I'm still waiting to gain confidence/test that this
 will be ok for folks without svn tools installed and/or a regular internet
 connection who have a copy of the snapshot to work with. Note the full
 release tarballs have the .svn/ stuff stripped away so in a full release
 `svnversion -c` or other tricks will not work.

 bumping the target up to the devel branches.


 Hamish

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/587#comment:41>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list