All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross.burton@arm.com>,
	 openembedded-core@lists.openembedded.org
Cc: nd@arm.com
Subject: Re: [OE-core] [PATCH][master] poky-tiny: fix PACKAGE_EXCLUDE
Date: Mon, 06 Nov 2023 10:44:57 +0000	[thread overview]
Message-ID: <f772002b508b7a29fec7957f072a33dee36bf627.camel@linuxfoundation.org> (raw)
In-Reply-To: <20231106103516.361162-1-ross.burton@arm.com>

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?

> 
> Signed-off-by: Ross Burton <ross.burton@arm.com>
> ---
>  meta-poky/conf/distro/poky-tiny.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-poky/conf/distro/poky-tiny.conf b/meta-poky/conf/distro/poky-tiny.conf
> index 32c2ec3e1fa..24bcbee9bb6 100644
> --- a/meta-poky/conf/distro/poky-tiny.conf
> +++ b/meta-poky/conf/distro/poky-tiny.conf
> @@ -125,4 +125,4 @@ PACKAGECONFIG:remove:pn-opkg-utils = "python"
>  
>  # 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?

Cheers,

Richard


  reply	other threads:[~2023-11-06 10:45 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 ` Richard Purdie [this message]
2023-11-06 10:55   ` [OE-core] " Ross Burton
2023-11-06 11:05     ` Richard Purdie

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