Replicant

h1. Replicant Sources

h2. Browsing the source

The Replicant source code is currently hosted at Gitorious: https://gitorious.org/replicant 

There is a branch per Replicant version, like @replicant-2.2@.

h2. Disk space

Before downloading the Replicant source code, make sure there is a considerable amount of disk space left on the drive you intent to build Replicant on.

It is advised to have 40-50GiB available for the Replicant source code and the produced files.

h2. Code tree location

Start by defining the place where you want to download Replicant tree.

*Important: the name of the path to this location must not contain spaces!*

h2. Installing the tools

Then, download the @repo@ tool and set it executable:

<pre>

mkdir tools

cd tools

wget http://commondatastorage.googleapis.com/git-repo-downloads/repo

chmod a+x repo

cd ../

</pre>

h2. Getting the source manifest

The source manifest is the list of all the git repositories that are present in the Replicant tree.

Each Replicant version has a dedicated branch with the proper source manifest.

h3. Replicant 4.2

<pre>

mkdir replicant-4.2

cd replicant-4.2

../tools/repo init -u git://gitorious.org/replicant/manifest.git -b replicant-4.2

</pre>

h3. Replicant 4.0

<pre>

mkdir replicant-4.0

cd replicant-4.0

../tools/repo init -u git://gitorious.org/replicant/manifest.git -b replicant-4.0

</pre>

h3. Replicant 2.3

<pre>

mkdir replicant-2.3

cd replicant-2.3

../tools/repo init -u git://gitorious.org/replicant/manifest.git -b replicant-2.3

</pre>

h3. Replicant 2.2

<pre>

mkdir replicant-2.2

cd replicant-2.2

../tools/repo init -u git://gitorious.org/replicant/manifest.git -b replicant-2.2

</pre>

h2. Downloading/Updating the source from the repos

Now that you have configured the repository to use a manifest, you can start downloading Replicant sources for the desired version.

*This step is very long and can take the whole day to complete!*

<pre>

../tools/repo sync

</pre>

Depending on your internet bandwidth, using the @-j@ argument may speed up the process (if you encounter errors, retry without the @-j@ argument):

<pre>

../tools/repo sync -j9

</pre>

Once the source is ready, you need to get the prebuilt applications (they are downloaded from F-Droid):

<pre>

vendor/replicant/get-prebuilts

</pre>

You must redo these steps each time you want to sync your tree, in order to keep it up to date. Future syncs are faster than the first one.