PINE64

If people are going to contribute code back to Pine, the source has to get under version control. Without version control is is chaos to contribute code back since you never know what to base it off from.

Currently you are posting tarballs...
http://wiki.pine64.org/index.php/Pine_A6...SP_Related

Some places like Gitlab allow repos up to 10GB in size. Can someone from Pine get this code checked into a version control system?  Pine people need to do this so that you will be the owner of the accounts.

Maybe an Android expert can help out with this. If should be possible to do a reposync to the main AOSP repository and then apply only the deltas needed for Allwinner A64 and Pine support.  These device specific delta should be fairly small. Is someone experienced at turning these tarballs back into deltas against the AOSP repos?

(04-14-2016, 03:38 PM)jonsmirl Wrote: [ -> ]If people are going to contribute code back to Pine, the source has to get under version control. Without version control is is chaos to contribute code back since you never know what to base it off from.

Currently you are posting tarballs...
http://wiki.pine64.org/index.php/Pine_A6...SP_Related

Some places like Gitlab allow repos up to 10GB in size. Can someone from Pine get this code checked into a version control system?  Pine people need to do this so that you will be the owner of the accounts.

Maybe an Android expert can help out with this. If should be possible to do a reposync to the main AOSP repository and then apply only the deltas needed for Allwinner A64 and Pine support.  These device specific delta should be fairly small. Is someone experienced at turning these tarballs back into deltas against the AOSP repos?

Thanks on your advise and the Pine64 wiki page now kind of messy and not organized well. I will take in your suggestion and work with the wiki team on next week.

Having the A64 Kernel and Device code in a repo would be fine, that's how some Android ROMs work.  If that repo is able to be dropped right into AOSP, that's a win-win scenario for the community.

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

These giant tarballs are not a good way to distribute Android source. It is very painful to contribute changes to them or to apply security updates.

(04-15-2016, 05:18 PM)jonsmirl Wrote: [ -> ]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

These giant tarballs are not a good way to distribute Android source. It is very painful to contribute changes to them or to apply security updates.

Noted and thanks on the example. We will review and make improvement on this week.