On Apr 18, 2007, at 8:48 PM, Ken Williams wrote:
On Apr 18, 2007, at 12:01 PM, Eric Wilhelm wrote:
What about an external tool for managing version numbers? That would
have wide applicability and could be used manually or linked into a
build action to encapsulate a given project's policy.
I've been thinking about this slowly for a few months. What I'd
like to do is add an option during 'Build dist' that rewrites all
'$VERSION = whatever' assignments to a static version. Determined
through the usual route of dist_version_from or dist_version.
I share the uneasiness about dynamically inherited versions at
runtime - it masks the scenario when two files were installed from
different versions of the distribution.
That sounds great. Like many others, I'm sure, I have my own cobbled
program to search-and-replace version numbers as part of my release
ritual. As an extension of that idea, it would be cool if distcheck
would report any inconsistent version numbers. But that could pose a
problem for the (irksome) packages which deliberately have different
version numbers for different modules. Maybe distcheck could only
report a problem if more than N modules but less than all have the
same version number? N could be 3-5, perhaps.
Chris
--
Chris Dolan, Equilibrious LLC, http://equilibrious.net/
Public key: http://chrisdolan.net/public.key
vCard: http://chrisdolan.net/ChrisDolan.vcf
