[PATCH] setup: include package/build/distribution id from HG_PACKAGE in version string

Steve Borho steve at borho.org
Wed Oct 27 20:05:04 CDT 2010


On Wed, Oct 27, 2010 at 8:01 PM, Steve Borho <steve at borho.org> wrote:
> On Wed, Oct 27, 2010 at 7:36 PM, Mads Kiilerich <mads at kiilerich.com> wrote:
>> # HG changeset patch
>> # User Mads Kiilerich <mads at kiilerich.com>
>> # Date 1288226146 -7200
>> # Branch stable
>> # Node ID 0de6a2a4db2a0bb234edafe74992d0e56a16be4b
>> # Parent  e1855dee28c164be291755af2e11b26efe77a64e
>> setup: include package/build/distribution id from HG_PACKAGE in version string
>>
>> When replying to "issues" we often have to ask which package/installer has been
>> used. This patch gives packagers a simple way of providing that information
>> by putting some kind of build tag in the Mercurial version string.
>>
>> It should be made "mandatory" for packagers to set this to something like
>> "TortoiseHg 1.2", "thg-winbuild", "thg-winbuild-2.6", "Berkwood", "Debian",
>> "Ubuntu", "Fedora", "pypi" etc. That would often make it easier to answer
>> support questions.
>
> Is this something we want in the version number?  I suspect many
> scripts try to parse that value.  I think I prefer storing a packager
> field in __version__.py that is echod by debuginstall and shown in
> backtrace headers.

Sorry, I should have read the full of the patch.  That's basically
what it does.  I think I'm fine with it except for the part that
annotates the output of 'hg version', unless we add extra output for
'hg version -v' or something.

-- 
Steve Borho


More information about the Mercurial-devel mailing list