From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: ecordonnier@snap.com
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [PATCH] lib/bb: Drop BBFILE_PRIORITY support
Date: Wed, 7 Feb 2024 23:27:41 +0100 [thread overview]
Message-ID: <202402072227419c816a19@mail.local> (raw)
In-Reply-To: <CAHUKmYY1fMCiNq36MzoeuQ5EKQYm_ZAEkkDuRUTeg94a+ZnubQ@mail.gmail.com>
On 06/02/2024 17:31:03+0100, Etienne Cordonnier via lists.openembedded.org wrote:
> Is the BBFILE_PRIORITY not controlling the order in which bbappends from
> different layers gets applied? I thought it was important e.g. when
> applying kernel configuration files (the last one to be applied override
> the previous ones).
I'd rather think this is in BBLAYERS list order
>
> On Tue, Feb 6, 2024 at 4:56 PM Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
> > On Tue, 2024-02-06 at 16:26 +0100, Etienne Cordonnier wrote:
> > > Hi Richard, there is a word missing in the commit message:
> > > " The functionality had a and place" -> "the functionality had a time
> > and place"
> > > Also a typo: "comparibility" -> " compatibility "
> >
> > Thanks, I'll tweak those on the branch.
> >
> > > What is the correct way to set layer priorities after this patch (I'm
> > > asking because the BSP I'm using makes use of BBFILE_PRIORITY)?
> >
> > It may set it, but what is it trying to achieve by setting it?
> >
> > As far as I know, the potential issue is needing to set specific
> > PREFERRED_VERSION entries where older recipes need to be used.
> >
> > Cheers,
> >
> > Richard
> >
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#15832): https://lists.openembedded.org/g/bitbake-devel/message/15832
> Mute This Topic: https://lists.openembedded.org/mt/104196430/3617179
> Group Owner: bitbake-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-02-07 22:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 12:15 [PATCH] lib/bb: Drop BBFILE_PRIORITY support Richard Purdie
2024-02-06 15:26 ` [bitbake-devel] " Etienne Cordonnier
2024-02-06 15:37 ` Martin Jansa
2024-02-06 15:56 ` Richard Purdie
2024-02-06 16:31 ` Etienne Cordonnier
2024-02-07 22:27 ` Alexandre Belloni [this message]
2024-06-27 12:55 ` Etienne Cordonnier
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=202402072227419c816a19@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=ecordonnier@snap.com \
--cc=richard.purdie@linuxfoundation.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.