From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gtk+-native-2.20.0-r8.0 fails in do_configure.
Date: Thu, 08 Apr 2010 17:55:02 +0200 [thread overview]
Message-ID: <hpku8m$a4p$1@dough.gmane.org> (raw)
In-Reply-To: <20100408162533.ae09c2c4.ospite@studenti.unina.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08-04-10 16:25, Antonio Ospite wrote:
> On Thu, 08 Apr 2010 16:15:57 +0200
> Koen Kooi <k.kooi@student.utwente.nl> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 08-04-10 16:11, Antonio Ospite wrote:
>>
>>> versioned dependencies are possible in .bb files
>>
>> Actually, they aren't. DISTROs should take care of stuff like this in
>> the current OE design.
>
> In what sense they are not possible?
You can add them, but the version will get ignored
> I can see some with
> git grep DEPENDS | grep '>='
> but that could be misleading me.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFLvfxVMkyGM64RGpERAj+/AJwPJm/oYtGh35gpUBAeit29Z4gJKQCcDCRE
duxFuFKdJp8aYVQzjT6SROw=
=G/m/
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-04-08 15:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 15:17 gtk+-native-2.20.0-r8.0 fails in do_configure Antonio Ospite
2010-04-03 18:17 ` Marcin Juszkiewicz
2010-04-06 9:58 ` Antonio Ospite
2010-04-08 9:22 ` Antonio Ospite
2010-04-08 9:54 ` Koen Kooi
2010-04-08 14:21 ` Antonio Ospite
2010-04-08 21:20 ` [PATCH] glib-2.0: remove old glib-2.0-native recipes Antonio Ospite
2010-04-08 21:33 ` Mike Westerhof
2010-04-08 22:50 ` Tom Rini
2010-04-09 7:51 ` Koen Kooi
2010-04-09 10:32 ` Michael 'Mickey' Lauer
2010-04-09 19:21 ` Antonio Ospite
2010-04-08 14:11 ` gtk+-native-2.20.0-r8.0 fails in do_configure Antonio Ospite
2010-04-08 14:15 ` Koen Kooi
2010-04-08 14:25 ` Antonio Ospite
2010-04-08 15:55 ` 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='hpku8m$a4p$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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox