Mozilla Mercurial Compilation Steps

[tripnixon]

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

uname

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

From: Mercurial Site : ​http://selenic.com/repo/hg-stable

​http://selenic.com/repo/hg-stableCurrent TGZ : Mercurial-stable-branch--bd23d5f28bbb.tar.gz

[tripnixon]

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

Repro :

1. Download stable build of Mercurial from ​http://selenic.com/repo/hg-stableCurrent
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

4. Run make local
5. Test Mercurial's install: cd ~ ; hq --version
6. Output should be:

Mercurial Distributed SCM (version 1.8.3+14-bd23d5f28bbb)

(see ​http://mercurial.selenic.com 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.

[tripnixon]

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 ​http://hg.mozilla.org/releases/mozilla-2.0/ /boot/home/20src/

3. 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>

[mmadia]

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

Unfortunately, this bug tracker isn't the place for the content. HaikuPorts, HTTP://ports.haiku-files.org is more appropriate. There is even an idle fork of the 1.8 codebase (Firefox 2.x) over at OsDrawer, ​http://dev.osdrawer.net/projects/bezilla. 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)

[tripnixon]

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