[PATCH 1 of 4 v2] debuginstall: add mercurial version

[timeless]

On Thu, May 26, 2016 at 8:27 AM, Yuya Nishihara <yuya at tcha.org> wrote:
> On Wed, 25 May 2016 22:27:47 -0400, timeless wrote:
>> Yuya Nishihara wrote:
>> > Just curious. What's the advantage over "hg version" ?
>>
>> Parsing hg version is annoying.
>
> We can add version -T.

Probably a good idea.

But the reason I want debuginstall, is that when you're asking for
debug information, you want all of this information (everything from
debuginstall), including the hg version. In fact, the first question
we need to ask is "what version are you running?"

Note: the next thing I'd probably like to add to debuginstall is the
list of enabled extensions. I haven't figured out which way I want
them.

One approach is:
{ "extensions":
  [
    "rebase"
  ]
}
Another is:
{ "extensions":
 {
  "rebase": "",
  "topics": "~/hg/topic/hgext3rd/topic/"
 }
}
But I think I'm going to lean toward:
{ "extensions":
 [
  {
   "name":"rebase",
   "version":"internal",
   "path":""
  },
  {
   "name":"topics",
   "version":"",
   "path":"~/hg/topic/hgext3rd/topic/"
  },
  {
   "name":"evolve",
   "version":"5.4.0",
   "path":"~/hg/evolve-main/hgext/evolve.py"
  }
 ]
}

We could require people to run:
hg version; hg debuginstall; hg extensions (*)
And thus:
hg version -T...; hg debuginstall -T...; hg extensions -T...
or, we could just allow:
hg debuginstall / hg debuginstall -T...

I'd rather debuginstall cover the bases. For extensions, it could
report about extensions that aren't supported (testedwith < version).