From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] PREMIRRORS ordering seem wrong?
Date: Wed, 13 Nov 2024 13:28:53 +0000 [thread overview]
Message-ID: <41a56a5b45abc5211b1d96fa236d59aa558bb489.camel@linuxfoundation.org> (raw)
In-Reply-To: <32aa4b12e3bafb565ddd362f1abbb67b6767d59a.camel@infinera.com>
On Wed, 2024-11-13 at 13:22 +0000, Joakim Tjernlund wrote:
> On Wed, 2024-11-13 at 12:49 +0000, Richard Purdie wrote:
> > On Wed, 2024-11-13 at 10:30 +0000, Joakim Tjernlund via
> > lists.openembedded.org wrote:
> > > I have set:
> > > INHERIT += "own-mirrors"
> > > PREMIRRORS:prepend = "my git pre mirror expr."
> > >
> > > looking at:
> > > bitbake -e my-image | grep PREMIRRORS=
> > > I see that "my git pre mirror expr." is last in PREMIRRORS
> > > variable,
> > > that seems wrong?
> > >
> > > To me "my git pre mirror expr." should be before the entries
> > > added by
> > > own-mirrors
> >
> > INHERIT in conf files is deferred and not immediately processed.
> >
>
> OK, that seems to support my findings as own-mirrors also does
> PREMIRRORS:prepend and that
> puts my own PREMIRRORS:prepend = "my git pre mirror expr." last in
> PREMIRRORS
>
> It that how it should be?
INHERIT has always been handled at the end of "conf file" parsing so
that isn't a bug.
The fact own-mirrors uses prepend is also as it has been for a long
time. Things are behaving as expected, the only question would be if
own-mirrors should do something differently but that could break other
users :/
Cheers,
Richard
prev parent reply other threads:[~2024-11-13 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 10:30 PREMIRRORS ordering seem wrong? Joakim Tjernlund
2024-11-13 12:49 ` [OE-core] " Richard Purdie
2024-11-13 13:22 ` Joakim Tjernlund
2024-11-13 13:28 ` Richard Purdie [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=41a56a5b45abc5211b1d96fa236d59aa558bb489.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Joakim.Tjernlund@infinera.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox