All of lore.kernel.org
 help / color / mirror / Atom feed
From: Detlef Vollmann <dv@vollmann.ch>
Cc: bitbake-dev <bitbake-devel@lists.openembedded.org>
Subject: Re: [oe] preferred version not available
Date: Tue, 19 Jul 2011 13:25:49 +0200	[thread overview]
Message-ID: <4E2569BD.4070300@vollmann.ch> (raw)
In-Reply-To: <201107191053.35867.paul.eggleton@linux.intel.com>

[Resend to bitbake-devel due to new list address]
On 07/19/11 11:53, Paul Eggleton wrote:
> On Tuesday 19 July 2011 08:20:00 Detlef Vollmann wrote:
>> On 07/18/11 23:05, Chris Larson wrote:
>>> All variables which are typically set by the filename can be
>>> overridden. Those are simply defaults. See the definitions of PN, PV,
>>> and PR in bitbake.conf.
>>
>> Yes, I knew that (I actually wrote the line changing the PV myself).
>> What surprised me (though it makes sense) that PREFERRED_VERSION
>> refers to PV, and not directly to a part of the filename.
>> It's probably still too much of 'make' history in my brain...
>
> I wonder if it would make sense to add something to the error message that
> also lists the available versions? Then it would be a little more obvious what
> you need to set PREFERRED_VERSION to.
That would be great.
And while we are in wishlist mode ;-) :
With a high enough debug level (I think 2), you'll get a list of
providers for a specific target.
To get also a list of versions for a specific package (PN), would
be really helpful.

   Detlef




  parent reply	other threads:[~2011-07-19 12:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 19:16 preferred version not available Detlef Vollmann
2011-07-18 21:02 ` Detlef Vollmann
2011-07-18 21:05   ` Chris Larson
2011-07-19  7:20     ` Detlef Vollmann
2011-07-19  9:53       ` Paul Eggleton
2011-07-19 10:16         ` Detlef Vollmann
2011-07-19 11:25         ` Detlef Vollmann [this message]
2011-07-19 15:06       ` Chris Larson

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=4E2569BD.4070300@vollmann.ch \
    --to=dv@vollmann.ch \
    --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.