Re: [RFC PATCH] allow arbitrary Linux kernel versions

[Esben Haabendal <esben dot haabendal at dev dot prevas dot dk>]

"Yann E. MORIN" <yann.morin.1998@free.fr> writes:

>> Ideally ct-ng would remember the major version and only
>> update the minor, e.g. from gcc-linaro-4.6-2012.08
>> to gcc-linaro-4.6-2012.09.
>
> OK, that's a sane idea.
>
> Currently, the config does (roughly!):
>
>     config GCC_V_linaro_4_6_2010_09
>         bool "linaro-4.6-2012.09"
>
>     config GCC_VERSION
>         string
>         default "linaro-4.6-2012.09" if GCC_V_linaro_4_6_2010_09
>
> This could be changed to:
>
>     config GCC_V_linaro_4_6
>         bool "linaro-4.6 (2012.09)"
>
>     config GCC_VERSION
>         string
>         default "linaro-4.6-2012.09" if GCC_V_linaro_4_6
>
> Thus, the new config would "maintain" the linaro 'major' selection, and
> only upgrade the 'minor' version. Is that the behavior you are suggesting?

I for one would like to see that minor change in behavior :-)

> And maybe we could use a similar scheme for other components, such as the
> Linux kernel:
>
>   - for the latest major release (eg. gcc-4.7 today), keep all sub-versions
>   - for previous major releases (eg. gcc-4.6, 4.5...), keep only the "major"
>     version ID in the config, and update the minor version only in the
>     "string" option, thus allowing to more easily forward a .config to a
>     newer ct-ng version.
>
> Could that be a correct answer to your issue?

+1 :-)

It would slightly easy upgrading of ct-NG in OE-lite.

/Esben

--
For unsubscribe information see http://sourceware.org/lists.html#faq