easily installing modern Mercurial on RHEL6

[Cody Scott]

I install Mercurial into a virtualenv and then create a symlink in a folder
that is on my $PATH.

I also install hg-git and hg-evolve in the same virtualenv with Mercurial.

https://bitbucket.org/Siecje/hg_setup/src/421e2c682e6706a4debf07a06109fed303a05ee2/Linux.md?at=default&fileviewer=file-view-default


On Fri, Oct 27, 2017 at 11:56 AM, Hollis Blanchard <
hollis_blanchard at mentor.com> wrote:

> I'm still waiting to see these RPMs, but I'm concerned about two things:
>
>    1. They need to be relocatable, so that non-root users can install
>    with 'rpm --prefix /foo'. This doesn't happen automatically:
>    $ rpm --prefix /scratch1/hblancha/tmp -ivh
>    https://www.mercurial-scm.org/release/centos6/RPMS/x86_64/
>    mercurial-4.0-0.9_rc.x86_64.rpm
>    <https://www.mercurial-scm.org/release/centos6/RPMS/x86_64/mercurial-4.0-0.9_rc.x86_64.rpm>
>    Retrieving https://www.mercurial-scm.org/release/centos6/RPMS/x86_64/
>    mercurial-4.0-0.9_rc.x86_64.rpm
>    <https://www.mercurial-scm.org/release/centos6/RPMS/x86_64/mercurial-4.0-0.9_rc.x86_64.rpm>
>    error: package mercurial is not relocatable
>    2. This is only mercurial core, not including hg-git, hg-experimental,
>    or liblz4.
>
> Unless I can find an rpm one-liner for all these packages, I don't think
> RPMs are going to solve this problem.
>
> Hollis Blanchard <hollis_blanchard at mentor.com> <hollis_blanchard at mentor.com>
> Mentor Graphics Emulation Division
>
> On 10/23/2017 02:13 AM, Mathias De Maré wrote:
>
>
>
> On Sat, Oct 14, 2017 at 11:22 PM, Gregory Szorc <gregory.szorc at gmail.com>
> wrote:
>
>> On Wed, Oct 11, 2017 at 7:15 PM, Hollis Blanchard <
>> hollis_blanchard at mentor.com> wrote:
>>
>>> I've been experimenting with building a modern Mercurial environment on
>>> RHEL6. I need to include some external extensions (hg_experimental and
>>> hg-git), but my distribution is ancient I'm not even an administrator. I
>>> wanted to make it as easy as possible to install this environment on
>>> anybody's workstation, to remove initial installation as a barrier to
>>> adoption.
>>>
>>> The attached script is not RHEL-specific, but it expects users to
>>> provide gcc 4.7 and python 2.7. I'm considering changing it to pull gcc 4.7
>>> and lz4 packages from EPEL, which would tie it to RHEL...
>>>
>>> It's certainly not a General Purpose Installer, but it works well for me
>>> and I'm sharing it in case it's useful to others in a similar situation.
>>> With improvements, would this be useful as a contrib/ script, or just a
>>> blog post somewhere?
>>>
>>
>> I believe previous discussions around supporting Mercurial on older RHEL
>> releases resulted in the decision to provide RPMs with a self-contained
>> Python installation. Essentially, you could `yum localinstall
>> /path/to/mercurial.rpm` and it would "just work." What I'm not sure is if
>> we ever landed code to produce those RPMs. If we did, we're not publishing
>> them to https://www.mercurial-scm.org/release/.
>>
> The producing of those RPMs works fine (we're using it for CentOS 5, 6 and
> 7). As soon as I get permission to send a public key, they will be
> published on  https://www.mercurial-scm.org/release/ (I am hoping for
> today).
>
>>
>> Of course, anything we can do to make installing a modern Mercurial on as
>> many machines as possible is a good idea. So if you feel others could
>> benefit from the script you wrote, I'd encourage you to send it as a patch.
>>
>> Augie: anything to add?
>>
>>
>> _______________________________________________
>> Mercurial mailing list
>> Mercurial at mercurial-scm.org
>> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>>
>>
>
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20171027/8b2cb60a/attachment-0002.html>