All of lore.kernel.org
 help / color / mirror / Atom feed
From: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
To: Leon Woestenberg <leon@sidebranch.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [yocto] dev-manual: differing versions of same recipe in different priority layers?
Date: Thu, 13 Feb 2020 11:26:27 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.21.2002131124270.2831500@localhost.localdomain> (raw)
In-Reply-To: <CAMjhiJimkmSzkGrw6Dfe6dN_tnwd-N9Y4MV3GGFYZ5Lgvoicog@mail.gmail.com>

On Thu, 13 Feb 2020, Leon Woestenberg wrote:

> Hello Robert,
>
> On Thu, Feb 13, 2020 at 3:14 PM rpjday@crashcourse.ca
> <rpjday@crashcourse.ca> wrote:
> >   in the YP dev manual, section 3.1.6, there is a maddeningly vague
> > note:
> >
> > "It is possible for a recipe with a lower version number PV in a layer
> > that has a higher priority to take precedence."
> >
> >   so does it take precedence or not? just saying it's "possible"
> > doesn't clarify it for the reader.
> >
> Yes, this should be re-worded. This is actually a FAQ.
> (I remember more sentences like this exist, that especially for
> non-English speakers might be difficult to interpret.)

  i'm betting i'm going to find all of them eventually. :-)

> My proposal would be:
>
> If a recipe exists in multiple layers, the recipe with highest PV
> *from the layer with the highest priority* is selected. Be aware
> that recipes with the same PN in lower priority layers are thus not
> selected, *even if their PV is higher*.

  right ... higher layer priority takes precedence over higher version
number. i'll submit something for that.

rday

      reply	other threads:[~2020-02-13 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13 14:14 dev-manual: differing versions of same recipe in different priority layers? rpjday
2020-02-13 15:45 ` [yocto] " Leon Woestenberg
2020-02-13 16:26   ` rpjday [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=alpine.LFD.2.21.2002131124270.2831500@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=leon@sidebranch.com \
    --cc=yocto@yoctoproject.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.