[oi-dev] review for 1619: Mercurial needs to transition to python2.6

[Richard Lowe]

>
> To try to put it briefly: if I were really moving forward, I'd that in
> oi-build (where a later version of Mercurial is already in place for
> sustaining). As I'm just doing some minor shifting (sideways instead of
> forward, as it were), it seemed simpler to do this with the existing
> build system, which I'm modestly tweaking for the package.
>

Yes, it's actually getting the resulting package out into the world
that's a pain.

I think what you did is the right way to do it, I'm just not sure that
it'll result in new packages actually being built and distributed...

-- Rich