directory name of unpacked tarball has to be checked each release

[Marcin Juszkiewicz]

Each time new tarball of Linaro cross toolchain is released it has date in directory name so path needs to be checked and cannot be assumed:

gcc-linaro-aarch64-linux-gnu-4.7-2013.03-20130313_linux
gcc-linaro-aarch64-linux-gnu-4.7-2013.03-20130318_linux
gcc-linaro-aarch64-linux-gnu-4.7-2013.04-20130415_linux
gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linux
gcc-linaro-arm-linux-gnueabihf-4.7-2013.04-20130415_linux

Can we get "gcc-linaro-TRIPLET-VERSION-RELEASE_linux" instead?

gcc-linaro-aarch64-linux-gnu-4.7-2013.04_linux
gcc-linaro-arm-linux-gnueabihf-4.7-2013.04_linux

[Marcin Juszkiewicz (hrw)]

Same issue with downloading tarballs - dates have to be checked each month and scripts updated.

[Zhenqiang Chen (zhenqiang-chen)]

The "date" (SPIN) is the binary build identifier, which is modified when creating the release candidate. It is necessary in case there are more than builds for one release.

[Matthew Gretton-Dann (matthew-gretton-dann)]

Can the date identifier be replaced by a spin number? 2013.04-0, 2013.04-1 for instance?

[Bernhard Rosenkraenzer (berolinux)]

AFAIK the SPIN= entry can be anything -- just not sure what it does to the automatically triggered builds...

[Zhenqiang Chen (zhenqiang-chen)]

Please note we might have updated source package release, e.g.

 gcc-linaro-4.7-2013.02-01.tar.bz2
 gcc-linaro-4.7-2013.02.tar.bz2

In this case, the gcc VERSION might be "4.7-2013.02-01". Even if we do not have SPIN, the package name is
gcc-linaro-4.7-2013.02-01_linux

If we have a updated binary release, the name will be

gcc-linaro-4.7-2013.02-01-1_linux

SPIN is just a number. If you think it is OK, we can remove it for the first release and add -1, -2, ... for the updated release.

[Zhenqiang Chen (zhenqiang-chen)]

I had removed the -$(SPIN) from the tarball name.

Then for the first release, the name will be:
gcc-linaro-aarch64-linux-gnu-4.7-2013.04_linux

Matt,
Who is the owner of cbuild? We need cbuild to support input from spawn (CROSSTOOL_NG_SPIN), just like how it handle CROSSTOOL_NG_TARGETS.

Bero,
Before cbuild support CROSSTOOL_NG_SPIN, we need update SPIN to -01, -02 and so on when respin is needed.

The release process (https://wiki.linaro.org/WorkingGroups/ToolChain/BinaryBuild/ReleaseProcess) is updated.

Thanks!
-Zhenqiang

[Viktor (vchong)]

Can we add a symbolic link in the release package that points to the directory name?