Hi,
On 25 June 2013 11:50, Nicolas Dechesne nicolas.dechesne@linaro.org wrote:
hi,
in meta-linaro-toolchain (dylan branch), the recipe points to gcc-linaro-4.7 from 1304 release:
https://git.linaro.org/gitweb?p=openembedded/meta-linaro.git%3Ba=blob%3Bf=me...
However that file seems to have be removed/cleaned from where the recipe expects it:
http://cbuild.validation.linaro.org/snapshots/
As such anyone build against that branch will now fails.
That brings some questions:
- How do we want to deal with that situation? Is
(http://snapshots.linaro.org/openembedded/sources) guaranteed to always keep all tarballs, forever? Or should we put such tarballs in such a place (and update recipes accordingly)? There can be non Linaro users of our layers (it's even referenced publicly here: http://layers.openembedded.org/layerindex/layer/meta-linaro-toolchain/)
As the name implies, it's snapshots builds: http://cbuild.validation.linaro.org/snapshots/ http://snapshots.linaro.org/openembedded
They are guaranteed to _not_ stay.
We (Linaro OE maintainers) should use stable, released tarballs.
That's the reason we have 2 lines for the SRC_URI: https://git.linaro.org/gitweb?p=openembedded/meta-linaro.git%3Ba=blob%3Bf=me...
When a toolchain release candidate is available, we switch to the snapshots build, but we should switch back to the released build as soon as it's available.
- most of the recent commits seem to go to master, not dylan. so it clearly
stated somewhere what our official requirements/committments are wrt to OE branch support?
We don't have any commitment wrt OE branch support. IMO, we should fix the URL to use https://releases.linaro.org/13.04/components/toolchain/gcc-linaro/4.7/gcc-li...
thanks
nicolas
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Cheers, -- Fathi Boudra Builds and Baselines Manager | Release Manager Linaro.org | Open source software for ARM SoCs