Project

General

Profile

SourceCode » History » Revision 8

Revision 7 (Paul Kocialkowski, 10/19/2013 08:22 PM) → Revision 8/51 (Linus Drumbler, 12/28/2013 11:04 PM)

h1. Getting 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. Code tree location 

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

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

 have no space!* 

 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 repos that are present in the Replicant tree. 
 There is one manifest per replicant version.  

 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 repo to use a manifest, you can start downloading Replicant sources for the desired version. 
 *This is 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, please retry without the @-j@ argument): 

 <pre> 
 ../tools/repo sync -j9 
 </pre> 

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