18GB Android tarball - source code done wrong

[jonsmirl]

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" />

[jonsmirl]

To break this down a little more, look at the nanopi manifest.

https://github.com/friendlyarm/android_m...efault.xml

There are two remotes:
aosp -- google's servers
origin -- repos nanopi has changed

Nanopi has changed about 15 repos...
those changed repos are on Github
https://github.com/friendlyarm?tab=repositories

All of the rest of their Android build is unmodified AOSP.

You can even use this scheme to pull Kodi into your build.

 <project path="device/friendly-arm/nanopi2" name="android_device_friendly-arm_nanopi2" remote="origin" revision="refs/heads/nanopi2-lollipop-mr1" groups="device,nanopi2" />
 <project path="frameworks/av" name="android_frameworks_av" remote="origin" groups="pdk" />
 <project path="frameworks/base" name="android_frameworks_base" remote="origin" groups="pdk-cw-fs" />
 <project path="frameworks/native" name="android_frameworks_native" remote="origin" groups="pdk" />
 <project path="frameworks/opt/net/ethernet" name="android_frameworks_opt_net_ethernet" remote="origin" />
 <project path="hardware/broadcom/libbt" name="android_hardware_broadcom_libbt" remote="origin" groups="pdk" />
 <project path="hardware/samsung_slsi/slsiap" name="android_hardware_samsung_slsi_slsiap" remote="origin" groups="slsiap" />
 <project path="packages/apps/Browser" name="android_packages_apps_Browser" remote="origin" revision="refs/heads/nanopi2-lollipop-mr1" />
 <project path="packages/apps/Settings" name="android_packages_apps_Settings" remote="origin" />
 <project path="system/core" name="android_system_core" remote="origin" groups="pdk" />
 <project path="system/vold" name="android_system_vold" remote="origin" groups="pdk" />
 <project path="vendor/broadcom/nanopi2" name="android_vendor_broadcom_nanopi2" remote="origin" revision="refs/heads/nanopi2-lollipop-mr1" />
 <project path="vendor/friendly-arm/build" name="android_vendor_friendly-arm_build" remote="origin" revision="refs/heads/nanopi2-lollipop-mr1" groups="nanopi2" />
 <project path="vendor/friendly-arm/nanopi2" name="android_vendor_friendly-arm_nanopi2" remote="origin" revision="refs/heads/nanopi2-lollipop-mr1" groups="nanopi2" />
 <project path="vendor/friendly-arm/apps" name="android_vendor_friendly-arm_apps" remote="origin" revision="refs/heads/nanopi2-lollipop-mr1" />
 <project path="vendor/nexell/s5p4418" name="nexell_platform_s5p4418" remote="origin" revision="refs/heads/nanopi2-lollipop-mr1" />
 <project path="vendor/nexell/apps" name="android_vendor_nexell_apps" remote="origin" />

---

So let's hope Allwinner is using the repo system.

First thing to do is to use repo to get a copy of their build.
Then look in the manifest and see which repos they have altered.

Use git push to push those alter repos up to github.
Make a new manifest that points to github and put it up on github.

Now this sequence will work

mkdir android && cd android
repo init -u https://github.com/pine64/android_manifest.git -b pine64-lollipop
repo sync

Add your own changes and push them up to github.

You also also able to use your tree to pull updates from Allwinner and then push them up to github.

And as a bonus! Android 6 is in the same AOSP repo.
You just need to change the tag you are using.

mkdir android && cd android
repo init -u https://github.com/pine64/android_manifest.git -b pine64-marshmellow
repo sync