All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: bitbake-devel@lists.openembedded.org
Subject: PREFERRED_VERSION and wildcards
Date: Wed, 14 Mar 2012 22:34:59 +0100	[thread overview]
Message-ID: <4F610F03.1070201@opendreambox.org> (raw)

Hi,

I just tried using wildcards, like it's done for gcc, e.g.:

PREFERRED_VERSION_foo = "1.2%"

Now, if I have two foo recipes, foo_1.2.1.bb and foo_1.2.3.bb, in the
same directory, then Bitbake always chooses 1.2.1 instead of the one
with the higher version number. Does bitbake always choose the first
matching version it can find? Is this a general limitation of wildcards,
or is this a problem that can get corrected? I'd expect it to choose the
highest matching version.

Regards,
Andreas



             reply	other threads:[~2012-03-14 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 21:34 Andreas Oberritter [this message]
2012-03-14 22:54 ` PREFERRED_VERSION and wildcards Martin Jansa
2012-03-14 23:53   ` Andreas Oberritter
2012-03-15  0:02     ` Martin Jansa

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=4F610F03.1070201@opendreambox.org \
    --to=obi@opendreambox.org \
    --cc=bitbake-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.