From edd at debian.org  Tue Mar 31 19:21:48 2009
From: edd at debian.org (Dirk Eddelbuettel)
Date: Tue, 31 Mar 2009 12:21:48 -0500
Subject: [Rd] Wishlist: optional svn-revision number tag in package
 DESCRIPTION file
In-Reply-To: <49D24BAF.7060405@stats.uwo.ca>
References: <gqta20$7ua$1@ger.gmane.org>
	<49D24BAF.7060405@stats.uwo.ca>
Message-ID: <18898.20780.532565.750117@ron.nulle.part>


On 31 March 2009 at 12:58, Duncan Murdoch wrote:
| On 3/31/2009 10:41 AM, Peter Ruckdeschel wrote:
| > Could we have one (or maybe more) standardized optional tag(s)
| > for package DESCRIPTION files to cover svn revision info?
| > This would be very useful for bug reporting...

Indeed. I am doing something similar with local packages at work.

| > I know that any developer is already free to append corresponding lines
| > to DESCRIPTION files to do something of this sort --- e.g. lines like
| > 
| > LastChangedDate: {$LastChangedDate: 2009-03-31 $}
| > LastChangedRevision: {$LastChangedRevision: 447 $}
| 
| That will give you the last change to the DESCRIPTION file, not the last 
| change to the package, so it could be misleading.  Last time I looked, 
| there wasn't a way in svn to auto update a file that wasn't involved in 
| a changeset.  (You could put something into your build script to call 
| svnversion, but I don't know anything simpler.)

Yes, I have been using configure for that (which can be really any type of
executable script rather than something from autoconf). One can then either
update a placeholder in DESCRIPTION.in to substitute the revision number
and/or create a package-local function reporting svn revision, build time,
etc.  

It may make sense to think about a more general scheme. A common problem is
of course once again portability and the set of required tools.

Dirk

-- 
Three out of two people have difficulties with fractions.



[Rd] Wishlist: optional svn-revision number tag in package DESCRIPTION file
Dirk Eddelbuettel