| 2015-06-24 15:38:47 |
Alex Tu |
description |
Per-talked with Caio on mail, Arale need a new feature that can repack factory images (flashable images) from the tarball downloaded from system-image.u.c.
[Description]
Currently we have a script "mkflashable.sh" can do that, and this is the usage of that script (it can be run without root privilege currently):
http://paste.ubuntu.com/11768175/
For example, generate factory images from the latest tarballs on channel "ubuntu-touch/rc/meizu.en"
$ ./mkflashable.sh --autobuild --channel ubuntu-touch/rc/meizu.en
The scenario will be like this:
1. Some one need to get a flashable image which map to latest release on system-image.u.c for flash-tool using (ex. make a factory image release).
2. That one can execute my script to download ubuntu, device, customer, version tarballs from latest release on the channel he want from system-image.u.c. Then unpack those tarballs and create images to include the content of unpacked tarballs.
And we also need a input box when execute this script on capomastro for parameters of mkflashable.sh.
ex. "--autobuild --channel ubuntu-touch/rc/meizu.en"
This is an example console output when executing "mkflashable.sh":
http://paste.ubuntu.com/11768243/
Finally user should can get the generated images in out/target/product/arale/flash-parts-full
or get its tarball "arale-flash-20150608-6e66f3c.tar.gz", "arale-flash-20150608-6e66f3c.tar.gz.md5sum" as well.
This is the generated images and its tarball list for reference:
http://paste.ubuntu.com/11768233/
BTW, we also need capamastro to do this on the code tree which based on branch "m75_ubuntu-daily" for manifest.
https://bugs.launchpad.net/capomastro/+bug/1386713/comments/3
[Conclusion]
So, the expect scenario with capomastro will like:
1. user input parameter in input box on capomastro. ex. "--autobuild --channel ubuntu-touch/rc/meizu.en" then kick it run.
2. capomastro checkout code based "m75_ubuntu-daily" on manifest.
ex. $ repo init -u ssh://git.tangxi.canonical.com:29418/m75/platform/manifest -b m75_ubuntu-daily ; repo sync
3. capomastro execute "mkflashable.sh" with user imputed parameters:
ex. $ ./mkflashable.sh --autobuild --channel ubuntu-touch/rc/meizu.en
4. capomastro let user can download generated tarball like "arale-flash-20150608-6e66f3c.tar.gz", "arale-flash-20150608-6e66f3c.tar.gz.md5sum" or files in out/target/product/arale/flash-parts-full |
Per-talked with Caio on mail, Arale need a new feature that can repack factory images (flashable images) from the tarball downloaded from system-image.u.c.
[Description]
Currently we have a script "mkflashable.sh" can do that, and this is the usage of that script (it can be run without root privilege currently):
http://paste.ubuntu.com/11768175/
For example, generate factory images from the latest tarballs on channel "ubuntu-touch/rc/meizu.en"
$ ./mkflashable.sh --autobuild --channel ubuntu-touch/rc/meizu.en
The scenario will be like this:
1. Some one need to get a flashable image which map to latest release on system-image.u.c for flash-tool using (ex. make a factory image release).
2. That one can execute my script to download ubuntu, device, customer, version tarballs from latest release on the channel he want from system-image.u.c. Then unpack those tarballs and create images to include the content of unpacked tarballs.
And we also need a input box when execute this script on capomastro for parameters of mkflashable.sh.
ex. "--autobuild --channel ubuntu-touch/rc/meizu.en"
This is an example console output when executing "mkflashable.sh":
http://paste.ubuntu.com/11768243/
Finally user should can get the generated images in out/target/product/arale/flash-parts-full
or get its tarball "arale-flash-20150608-6e66f3c.tar.gz", "arale-flash-20150608-6e66f3c.tar.gz.md5sum" as well.
This is the generated images and its tarball list for reference:
http://paste.ubuntu.com/11768233/
BTW, we also need capamastro to do this on the code tree which based on branch "m75_ubuntu-daily" for manifest.
https://bugs.launchpad.net/capomastro/+bug/1386713/comments/3
This feature also can be used on other project in the future, just need some change in script.
[Conclusion]
So, the expect scenario with capomastro will like:
1. user input parameter in input box on capomastro. ex. "--autobuild --channel ubuntu-touch/rc/meizu.en" then kick it run.
2. capomastro checkout code based "m75_ubuntu-daily" on manifest.
ex. $ repo init -u ssh://git.tangxi.canonical.com:29418/m75/platform/manifest -b m75_ubuntu-daily ; repo sync
3. capomastro execute "mkflashable.sh" with user imputed parameters:
ex. $ ./mkflashable.sh --autobuild --channel ubuntu-touch/rc/meizu.en
4. capomastro let user can download generated tarball like "arale-flash-20150608-6e66f3c.tar.gz", "arale-flash-20150608-6e66f3c.tar.gz.md5sum" or files in out/target/product/arale/flash-parts-full |
|
