Project

General

Profile

SourceCodeRepositories » History » Version 3

Wolfgang Wiedmeyer, 05/02/2017 02:14 PM
more details for update process

1 1 Wolfgang Wiedmeyer
h1. LineageOS Mirror
2
3
h2. Initial setup
4
5
Initialize the repository and sync:
6
<pre>
7
mkdir lineage_mirror
8
cd lineage_mirror
9
repo init -u https://git.replicant.us/replicant/manifest.git -b LineageOS-mirror
10
repo sync
11
</pre>
12
13
h2. Updating
14
15
# Check the LineageOS manifest for newly added repos
16 3 Wolfgang Wiedmeyer
# If there are any, add them in the LineageOS-mirror manifest and push the changes to git.replicant.us
17
# If there are any, create the newly added repos in the LineageOS-mirror group (using the exact same names the repos have in LineageOS)
18 1 Wolfgang Wiedmeyer
# Update the local mirror with @repo sync@
19 3 Wolfgang Wiedmeyer
# If there are newly added repos, you need to manually push them the first time in order to create the branch on the remote:
20
<pre>
21
cd path/to/new/repo
22
git push git@git.replicant.us:LineageOS-mirror/REPO_NAME HEAD:refs/heads/cm-13.0
23
</pre>
24
  Repeat these steps for all newly added repos.
25 1 Wolfgang Wiedmeyer
# Push the updated branches to git.replicant.us:
26 2 Wolfgang Wiedmeyer
<pre>
27
repo forall -c ' echo "Pushing $REPO_PROJECT"; git push git@git.replicant.us:LineageOS-mirror/$( echo $REPO_PROJECT | cut -c11- ).git HEAD:cm-13.0 '
28
</pre>
29
  Check for fatal errors during the push and fix them!
30 1 Wolfgang Wiedmeyer
31
h2. Notes
32
33
h3. Bundles
34
35
It's worth to check if all mirror repos have bundles in place.
36
37
h3. CAF variants
38
39
If we ever add support for a device that uses CAF branches of Qualcomm repos, we need to figure out how the mirror can still be updated and how releases can be tagged.
40
41
CAF branches are in the same repos as the default branches. So two or more local repos are created for one remote repo when the default branch and the CAF branches are checked out. The current setup for tagging a new release and updating the mirror assumes that there is one local repo for one remote repo.