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...
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
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.
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
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
On 3 May 2012 16:55, Zach Pfeffer zach.pfeffer@linaro.org wrote:
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?
assigned to me.
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
-- 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
On Thu, May 3, 2012 at 3:55 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
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?
I won't hold anybody back, but in general I don't think Fathi is the right person to fix this. This either would come from Android team if the current prebuilt image production is hooked in your platform build system or it has to go to the infrastructure team who probably would reach out to Andy.
In anycase, I believe we should take a step back and collect all the improvements we want to see and think them through properly. This includes the build config in git feature that isn't complete and shouldn't be used until a few points are addressed.
Please collect ideas and feature requests we want and schedule a connect session with andy, fathi, infra folks involved.
On 3 May 2012 09:23, Alexander Sack asac@linaro.org wrote:
On Thu, May 3, 2012 at 3:55 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
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?
I won't hold anybody back, but in general I don't think Fathi is the right person to fix this. This either would come from Android team if the current prebuilt image production is hooked in your platform build system or it has to go to the infrastructure team who probably would reach out to Andy.
Since the infrastructure team is pretty much offline, I think we should just see who can do the work.
In anycase, I believe we should take a step back and collect all the improvements we want to see and think them through properly. This includes the build config in git feature that isn't complete and shouldn't be used until a few points are addressed.
This is an easy improvment. No need to overthink and overplan things here.
Please collect ideas and feature requests we want and schedule a connect session with andy, fathi, infra folks involved.
Like I said, its just a bug. We have that collection of things, its in my one-on-ones with Danilo document where its all prioritized and ready to go.
-- Alexander Sack Technical Director, Linaro Platform Teams http://www.linaro.org | Open source software for ARM SoCs http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
On Thu, May 3, 2012 at 4:33 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 3 May 2012 09:23, Alexander Sack asac@linaro.org wrote:
On Thu, May 3, 2012 at 3:55 PM, Zach Pfeffer zach.pfeffer@linaro.org wrote:
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?
I won't hold anybody back, but in general I don't think Fathi is the right person to fix this. This either would come from Android team if the current prebuilt image production is hooked in your platform build system or it has to go to the infrastructure team who probably would reach out to Andy.
Since the infrastructure team is pretty much offline, I think we should just see who can do the work.
In anycase, I believe we should take a step back and collect all the improvements we want to see and think them through properly. This includes the build config in git feature that isn't complete and shouldn't be used until a few points are addressed.
This is an easy improvment. No need to overthink and overplan things here.
Please collect ideas and feature requests we want and schedule a connect session with andy, fathi, infra folks involved.
Like I said, its just a bug. We have that collection of things, its in my one-on-ones with Danilo document where its all prioritized and ready to go.
All I know is that I haven't seen a proper plan of what features are needed and how we want to approach them...
I feel there is risk of us coming up with few sub-standard solutions that loose the big picture or at least loose me, so please put that up and I am happy to provide input, sign off and work on the resource allocation and priority.
linaro-android@lists.linaro.org
-
Akira Tsukamoto -
Alexander Sack -
Fathi Boudra -
Zach Pfeffer