Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#7549 closed enhancement (invalid)

Mozilla Mercurial Compilation Steps

Reported by: tripnixon Owned by: nielx
Priority: normal Milestone: R1
Component: Documentation Version: R1/alpha2
Keywords: Mercurial Cc:
Blocked By: Blocking:
Platform: All


In an effort to work with projects, mainly FireFox, documenting process to install and leverage Mercurial in:


Haiku shredder 1 hrev36769 May 8 2010 20:58:31 BePC Haiku

From: Mercurial Site : TGZ : Mercurial-stable-branch--bd23d5f28bbb.tar.gz

Change History (4)

comment:1 by tripnixon, 11 years ago

Effort: to install Mercurial as to promote source check-outs of Mozilla projects.

Repro :

  1. Download stable build of Mercurial from
  2. Unpack distro : tar -zxvf <mercurial-stable-build>
  3. Create a /usr/sbin directory

3.1 Create symbolic link to hg reference, env : ln -s /usr/sbin/env /bin/env 3.2 Alternate solution is to adjust make reference to use /bin/env

  1. Run make local
  2. Test Mercurial's install: cd ~ ; hq --version
  3. Output should be:

Mercurial Distributed SCM (version 1.8.3+14-bd23d5f28bbb)

(see for more information)

Copyright (C) 2005-2011 Matt Mackall and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

comment:2 by tripnixon, 11 years ago

With successful build and version response, to checkout a project - such as mozilla 2.x src - execute the following:

  1. cd ~
  2. You *must* make the target path to help Mercurial, "hg", for check-outs:

2.1. mkdir ~/20src 2.2. To grab the clone of the src repo, per Mercurial/Mozilla's docs, execute:

~> hg clone /boot/home/20src/

  1. Output from the hg clone process may be slow as, per Mercurial.Mozilla, there is much data to be downloaded from Mozilla's source repo, but should reflect the following if hq has been compiled with access to the ENV variables for Haiku:

requesting all changes adding changesets adding manifests adding file changes <etc>

comment:3 by mmadia, 11 years ago

Resolution: invalid
Status: newclosed

Greetings and thanks for your interest in furthering Mozilla on Haiku!

Unfortunately, this bug tracker isn't the place for the content. HaikuPorts, HTTP:// is more appropriate. There is even an idle fork of the 1.8 codebase (Firefox 2.x) over at OsDrawer, That repository contains several ReadMe's, whichetail the various build steps.

Lastly, some of the steps in your instructions are not appropriate for porting or building software in Haiku (creating /usr and the other similar hacks)

comment:4 by tripnixon, 11 years ago

I am a noob to this, so thnx for the point in the right direction!

Note: See TracTickets for help on using tickets.