|
|
|
Asus has not posted updates for tinkerboard in 3-4 months, I think it unlikely that they will do so. Here is the process that i used to update our repo with their changes.
|
|
|
|
|
|
|
|
### Background
|
|
|
|
|
|
|
|
There are 3 "types" of projects.
|
|
|
|
1. Projects we own entirely
|
|
|
|
2. Projects we do not touch
|
|
|
|
3. Projects we modify from source
|
|
|
|
|
|
|
|
Projects 1 and 2 are simple to update, project type 3 is more difficult but usually pretty easy.
|
|
|
|
|
|
|
|
|
|
|
|
### Preparation
|
|
|
|
You will need a enough space for a full repo sync of asus' build.
|
|
|
|
Sync asus' Android 7 repo into a location. Go to build it once and repo will generate a manifest.xml file with rel="" tags that indicate the current build head.
|
|
|
|
Diff asus' manifest.xml file against ours. I collect a list of projects that changed or moved from the asus manifest and check them one by one against our manifest. Updating each by the procedures below.
|
|
|
|
|
|
|
|
#### Updating Projects entirely ours
|
|
|
|
Repo sync once the code is in the branch noted in the manifest should update it. No changes needed to manifest.
|
|
|
|
|
|
|
|
#### Updating Projects we do not touch
|
|
|
|
Take the commit ID from the asus manifest and put it into our manifest.
|
|
|
|
|
|
|
|
#### Updating projects we do touch.
|
|
|
|
Go to the project, add asus as a remote, merge their changes into our code. Remove the asus repo. Push this branch up. Most of these do not use a specific commit for the manifest, if they do, update the commit to the new head. |
|
|
\ No newline at end of file |
