When debugging the dev-python/python-twitter-9999.ebuild (see http://bugs.gentoo.org/show_bug.cgi?id=300967) lately, we were struggling with finding a way to specify the branch to use. binki/Nathan then pointed out that, surprisingly, EHG_REVISION is not limited to holding a changeset ID or tag, but can also hold a branch name (in our case: EHG_REVISION="default"). It would be cool (and likely of great help to many) if this fact, i.e. the versatility of EHG_REVISION, could be documented somehow (e.g. in mercurial.eclass). Thanks!
EHG_REVISION is passed directly to mercurial as value of --rev parameter and what you've described is documented in `hg help revisions' output: Any other string is treated as a tag or branch name. A tag name is a symbolic name associated with a revision identifier. A branch name denotes the tipmost revision of that branch. Tag and branch names must not contain the ":" character. I've modified description to mention `hg help revisions': # @DESCRIPTION: # Create working directory for specified revision, defaults to tip. +# +# EHG_REVISION is passed as a value for --rev parameter, so it can be more than +# just a revision, please consult `hg help revisions' for more details.
Thanks, Krzysiek!
