Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <Ross.Burton@arm.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH][master] poky-tiny: fix PACKAGE_EXCLUDE
Date: Mon, 06 Nov 2023 11:05:46 +0000	[thread overview]
Message-ID: <bc84dc8a84bed4bcd8b27bf9f73451c38186ee7b.camel@linuxfoundation.org> (raw)
In-Reply-To: <5A07D8A2-2FE1-4FD1-9468-0AF32FB335C9@arm.com>

On Mon, 2023-11-06 at 10:55 +0000, Ross Burton wrote:
> On 6 Nov 2023, at 10:44, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> > 
> > On Mon, 2023-11-06 at 10:35 +0000, Ross Burton wrote:
> > > From: Ross Burton <ross.burton@arm.com>
> > > 
> > > poky-tiny does a PACKAGE_EXCLUDE on shadow-base as the kernel doesn't
> > > support multiple users.  However it does this by assigning to an
> > > override, which makes it impossible for images or machines to extend
> > > PACKAGE_INCLUDE with their own exclusions.
> > 
> > PACKAGE_INCLUDE?
> 
> More coffee needed. V2 incoming.
> 
> > > # If shadow-base is brought into the image, logins will fail because it
> > > # doesn't have the heuristics to work when CONFIG_MULTIUSER is unset.
> > > -PACKAGE_EXCLUDE:poky-tiny = "shadow-base"
> > > +PACKAGE_EXCLUDE += "shadow-base"
> > 
> > Does yocto-check-layer still pass?
> 
> This is in the distro configuration so it still does nothing when not included, but:
> 
> INFO: meta-poky … PASS

Of course, that was the detail I was overlooking, thanks :)

Cheers,

Richard


      reply	other threads:[~2023-11-06 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 10:35 [PATCH][master] poky-tiny: fix PACKAGE_EXCLUDE ross.burton
2023-11-06 10:44 ` [OE-core] " Richard Purdie
2023-11-06 10:55   ` Ross Burton
2023-11-06 11:05     ` 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=bc84dc8a84bed4bcd8b27bf9f73451c38186ee7b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Ross.Burton@arm.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