[oe] [oe-commits] Koen Kooi : angstrom: sync pango and pango-native versions

[Koen Kooi]

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

On 02-03-10 21:43, Martin Jansa wrote:
> On Tue, Mar 02, 2010 at 01:14:10PM +0100, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 01-03-10 22:55, Holger Hans Peter Freyther wrote:
>>> On Monday 01 March 2010 22:37:23 Andrea Adami wrote:
>>>> Thx, but after this patch I see
>>>>
>>>> NOTE: preferred version 1.24.4 of pango-native not available (for item
>>>> pango-module-basic-x)
>>>> NOTE: preferred version 1.24.4 of pango-native not available (for item
>>>> pango-module-basic-fc)
>>>> NOTE: preferred version 1.24.4 of pango-native not available (for item
>>>> pango-native)
>>>
>>> mea culpa, I asked koen to bump it.. and he blindly did. The fix should be to 
>>> add a pango-native of that version.
>>
>> Yes, my bad! I had an extension to pango.inc sitting in my tree that I
>> didn't commit yet, but it's in now:
>>
>> http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=f45f0d3495aba36aafc286d25f96d5bd9a82c7d9
>>
>> This commit also shows that using BBCLASSEXTEND isn't so hard, more
>> people should try to convert their recipes to it instead of deleting them :)
>>
>> regards,
>>
>> Koen
> 
> Thanks Koen!
> 
> small issue:
> the same .inc is also used from
> pango-native_1.22.0.bb -> pango_1.22.0.bb -> pango.inc
> 
> So then it creates native-native and says
> NOTE: multiple providers are available for pango-native (pango-native,
> pango-native-native);
> NOTE: consider defining PREFERRED_PROVIDER_pango-native
> 
> I guess that git rm -r pango-native_1.22.0.bb pango-native-1.22.0
> is right sollution in this case but didn't checked it.

I was thinking of doing that, but didn't have the motivation to RFC it.
YOu have my ack to delete it :)

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLjXyXMkyGM64RGpERAhqFAJ9pjnXqAEch29GXzD9PSEG3aR+TowCaA80H
2IZrIux+V/OjqftQTmHWd8E=
=2F8v
-----END PGP SIGNATURE-----