SourceCode » History » Revision 40
« Previous |
Revision 40/51
(diff)
| Next »
Denis 'GNUtoo' Carikli, 08/06/2019 12:01 PM
Don't use vulnerable short keys handles. The long key was verified with the following trust chain my key -> Pauk Kocialkowski -> Hans-Christoph Steiner -> F-Droid. Thanks to Jeremy_Rand_Talo on IRC for the bugreport.
Replicant source code¶
Browsing the source code¶
The Replicant source code is currently hosted by the FSF at: git.replicant.us
There is one branch per Replicant version, such as replicant-2.2
.
Disk space¶
Before downloading the Replicant source code, make sure there is a considerable amount of disk space left on the drive you intend to build Replicant on.
It is advised to have 60-70GiB available for the Replicant source code and the produced files for one device. If you intend to build for multiple devices, every additional device will need ca. 17GiB.
Source tree root folder¶
The path to the source tree root folder must not contain spaces.
Installing the repo tool¶
To be able download the complete source code, the repo
tool needs to be installed. The distribution you are using may already have the tool packaged and it may already been installed as part of the Build dependencies installation.
It is recommended to install the repo
tool with the package manager. However, if the repo
tool is not available on your system, you can download and install it locally:
mkdir tools cd tools wget https://commondatastorage.googleapis.com/git-repo-downloads/repo chmod a+x repo cd ../
In the following, it is assumed that repo
is installed from your system's package manager. If you have installed repo
locally in ../tools/repo
, replace
repo
with
../tools/repo
at the beginning of the following commands.
Initializing the repository¶
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.
Replicant 6.0 release version¶
mkdir replicant-6.0 cd replicant-6.0 repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-6.0
Replicant 6.0 development version¶
mkdir replicant-6.0-dev cd replicant-6.0-dev repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-6.0-dev
Replicant 4.2¶
mkdir replicant-4.2 cd replicant-4.2 repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-4.2
Replicant 4.0¶
mkdir replicant-4.0 cd replicant-4.0 repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-4.0
Replicant 2.3¶
mkdir replicant-2.3 cd replicant-2.3 repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-2.3
Replicant 2.2¶
mkdir replicant-2.2 cd replicant-2.2 repo init -u https://git.replicant.us/replicant/manifest.git -b replicant-2.2
Downloading/Updating the source code¶
Now that you have configured repo
, you can start downloading Replicant sources for the desired version.
This step is very long and can take hours to complete!
repo sync
For the Replicant 6.0 release branch, it is possible and recommended to verify the signatures of the Git tags in all repositories:ReplicantSourceCodeTagsVerification
Prebuilt apps¶
Once the source code is ready, you need to get the prebuilt applications (they are downloaded from F-Droid). Since Replicant 6.0, the prebuilt applications are checked if they were signed with the F-Droid signing key. The signing key can be retrieved and added to your GPG keyring using:
gpg --recv-key 37D2C98789D8311948394E3E41E7044E1DBA2E89
Then you can download the prebuilts:
vendor/replicant/get-prebuilts
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.
Updated by Denis 'GNUtoo' Carikli over 5 years ago · 40 revisions