On 2 May 2012 16:04, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 19 April 2012 21:48, Akira Tsukamoto akira.tsukamoto@linaro.org wrote:
Hi,
The current Android LEB image has good name convention and I like it very much.
If it is possible, I would appreciate to have build number in the file name too. For example currently: at http://releases.linaro.org/12.03/android/leb-panda/ has panda-ics-gcc46-tilt-tracking-blob.img.gz but it is not clear from the file name that which build have been used for creating this image from bellow link: https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-tilt...
We actually handle this in a different way. If you look at the git log of the manifest git you can tell exactly which build the release came from. Do this:
git clone git://android.git.linaro.org/platform/manifest.git cd manifest/ git checkout linaro-android-12.04-release git log
...and you can get a list of which build the release came from. To make double sure you can compare the source-manifest.xml from a release pinned-manifest.xml. If their the same then you;ve found the build you're looking for.
Okay, I filed a bug at, https://bugs.launchpad.net/linaro-android/+bug/993986 to address this issue. Fathi are you interested in looking at this?
How about having build number at the end of file name like <target>-<android>-<toolchain>-<kernel_origin>-<kernel_type>-<enablement_type>-<build> panda-ics-gcc46-tilt-tracking-blob-6.img.gz for https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc46-tilt...
It makes easier to find where is the original contents for the created binary image just by the file name.
Regards,
Akira
-- Zach Pfeffer Android Platform Team Lead, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog