All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: design question: should layer.conf contain "PREFERRED_VERSION" settings?
Date: Wed, 22 Mar 2017 16:32:01 +0000	[thread overview]
Message-ID: <1490200321.13980.177.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJTo0LZV4kh3=r=cxYpBydGO74R6cvootczedwMW3s_k1xxSWQ@mail.gmail.com>

On Wed, 2017-03-22 at 15:44 +0000, Burton, Ross wrote:
> 
> On 22 March 2017 at 14:59, Richard Purdie <richard.purdie@linuxfounda
> tion.org> wrote:
> > What should happen is that the openstack recipe should complain
> > loudly
> > (error) if anyone tried to build it (or parse it?) with anything
> > except
> > the versions its known to work with.
> > 
> Is this a good time to bring up versions in DEPENDS?

Yes. I'd swear there was a bug for this but I can't find it. I know we
made versions able to be added to DEPENDS without parse failures, its
just a question of getting bitbake to parse them.

> It would be awesome to automatically set PREFERRED_VERSION as
> appropriate depending on the constrains in DEPENDS, but I'd be really
> happy with errors if the versions specified were not selected.
> 
> So in this case openstack could do DEPENDS=python-something (>4.0)
> and bitbake would error out if python-something v3 is being built.

I don't think setting PREFERRED_VERSION magically would be good but I
do like the rest of the idea, its always been the intent really...

Someone needs to file a bug...

Cheers,

Richard


  reply	other threads:[~2017-03-22 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-22 11:14 design question: should layer.conf contain "PREFERRED_VERSION" settings? Robert P. J. Day
2017-03-22 11:19 ` Burton, Ross
2017-03-22 11:57   ` Bruce Ashfield
2017-03-22 12:02     ` Burton, Ross
2017-03-22 12:14       ` Bruce Ashfield
2017-03-22 12:24         ` Robert P. J. Day
2017-03-22 12:33           ` Bruce Ashfield
2017-03-22 12:53             ` Robert P. J. Day
2017-03-22 14:59             ` Richard Purdie
2017-03-22 15:44               ` Burton, Ross
2017-03-22 16:32                 ` Richard Purdie [this message]
2017-03-24 13:54                   ` Burton, Ross
2017-03-22 17:02                 ` Bruce Ashfield
2017-03-22 15:37             ` Daniel Dickinson

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=1490200321.13980.177.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.