Re: native preferences

[Koen Kooi <k.kooi@student.utwente.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 26-07-10 14:08, Frans Meulenbroeks wrote:
> 2010/7/26 Koen Kooi <k.kooi@student.utwente.nl>
> 
> On 26-07-10 11:42, Florian Boor wrote:
>>>> Hi all,
>>>>
>>>> I tried to build a "minimal" distribution image lately and ran into some
> trouble
>>>>  because the old-style native packages seem to be preferred over the new
> ones
>>>> using BBCLASSEXTEND.
>>>> In this case we have glib-2.0-native 2.24.1 provided by the new mechanism
> and
>>>> 2.22.1 gets build which is the latest old-style native bb.
> 
> That's minimals broken by design behaviour, it refuses to pin any
> version. So either pin the version or switch to a sane distro like
> angstrom or shr.
> 
> 
> 
>> Hm. I would expect that if there is a glib-2.0 recipe 2.24.1 with
>> BBCLASSEXTEND = "native" and  no pinning and no DEFAULT_PREFERENCE being in
>> effect, that 2.24.1 gets build and not 2.22.1 which has a real native
>> recipe. To me recipes with -native and implict ones with BBCLASSEXTEND =
>> "native" are equivalent prioritywise, so I'd say this is a bug in the class
>> code.

And that bug has been known for months and reported multiple times by
people attempting to use minimal. And for so far the bug has been fixed
in bitbake 1.10, but minimal still refuses to pin versions, so the
advice to switch distro still stands.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMTX37MkyGM64RGpERArnKAJ9jd/pPEhb/XdRXTJstqJq0/5zD6ACfSToc
5nInC0ZKEPbp3x1zlBNPuDI=
=IBvv
-----END PGP SIGNATURE-----