05-27-2016, 02:38 PM
You don't need a 18GB tarball for Android source. That is a truly awful way to distribute Android source code.
Odroid-C2 is a good example of an Android repository done right.
http://odroid.com/dokuwiki/doku.php?id=e...ng_android
NanoPi Android build is similar
http://wiki.friendlyarm.com/wiki/index.p...le_Android
The basic idea.... get the core Android source code from Google's servers using the repo tool. That will be 95% of the code. Then you make up another set of repositories with your A64 specific changes. Those repositories will be small and will easily fit on Github where you can store them for free.
I am not sure yet what was done in the 18GB dump. It looks like some use of the repo tool was made, but this is definitely not the right way to do it. You guys need to get this sorted out, it is very difficult to split this tarball back into repositories belonging to Google, Allwinner and Pine64.
When you get this setup right you will only need to do this....
mkdir android && cd android
repo init -u https://github.com/pine64/android_manifest.git -b pin64-lollipop
repo sync
The repo sync tool will download all of the source code, 95% will come from Google's servers and the rest will come from Github.
Is Allwinner using the repo tool or are they dumping a tarball to you?
This is the key bit...
<remote name="aosp"
fetch="https://android.googlesource.com" />
<remote name="origin"
fetch="."
revision="refs/heads/s5p4418-lollipop-mr1" />
<default revision="refs/tags/android-5.1.1_r6"
remote="aosp"
sync-j="4" />
See how it is fetching most of the code from the public AOSP servers?
You have this, which must be some internal git server.
<remote name="exdroid"
fetch="/git_repo/A64/5.1/android" />
<default revision="develop"
remote="exdroid"
sync-j="4" />
Odroid-C2 is a good example of an Android repository done right.
http://odroid.com/dokuwiki/doku.php?id=e...ng_android
NanoPi Android build is similar
http://wiki.friendlyarm.com/wiki/index.p...le_Android
The basic idea.... get the core Android source code from Google's servers using the repo tool. That will be 95% of the code. Then you make up another set of repositories with your A64 specific changes. Those repositories will be small and will easily fit on Github where you can store them for free.
I am not sure yet what was done in the 18GB dump. It looks like some use of the repo tool was made, but this is definitely not the right way to do it. You guys need to get this sorted out, it is very difficult to split this tarball back into repositories belonging to Google, Allwinner and Pine64.
When you get this setup right you will only need to do this....
mkdir android && cd android
repo init -u https://github.com/pine64/android_manifest.git -b pin64-lollipop
repo sync
The repo sync tool will download all of the source code, 95% will come from Google's servers and the rest will come from Github.
Is Allwinner using the repo tool or are they dumping a tarball to you?
This is the key bit...
<remote name="aosp"
fetch="https://android.googlesource.com" />
<remote name="origin"
fetch="."
revision="refs/heads/s5p4418-lollipop-mr1" />
<default revision="refs/tags/android-5.1.1_r6"
remote="aosp"
sync-j="4" />
See how it is fetching most of the code from the public AOSP servers?
You have this, which must be some internal git server.
<remote name="exdroid"
fetch="/git_repo/A64/5.1/android" />
<default revision="develop"
remote="exdroid"
sync-j="4" />
