From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Koen Kooi : angstrom: sync pango and pango-native versions
Date: Tue, 02 Mar 2010 22:01:11 +0100 [thread overview]
Message-ID: <hmjuan$9v8$1@dough.gmane.org> (raw)
In-Reply-To: <20100302204327.GI3206@jama>
-----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-----
prev parent reply other threads:[~2010-03-02 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Nm0HI-0004Qt-Pn@melo.openembedded.org>
2010-03-01 21:37 ` [oe-commits] Koen Kooi : angstrom: sync pango and pango-native versions Andrea Adami
2010-03-01 21:55 ` Holger Hans Peter Freyther
2010-03-02 12:14 ` Koen Kooi
2010-03-02 12:31 ` Frans Meulenbroeks
2010-03-02 20:43 ` Martin Jansa
2010-03-02 21:01 ` Koen Kooi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='hmjuan$9v8$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.