Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: hongxu <hongxu.jia@windriver.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/3] apt: add nativesdk support
Date: Fri, 15 Jan 2021 11:26:59 +0000	[thread overview]
Message-ID: <adca85be61ff1fa0f2c4cb0d4a2093daa0d65b48.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210115094536.18651-2-hongxu.jia@windriver.com>

On Fri, 2021-01-15 at 17:45 +0800, hongxu wrote:
> 1. Add nativesdk support
> - Apply the same patches of native
> - Generate the same apt.conf.sample of native
> 
> 2. Create user '_apt' to fix apt runtime warning
> [snip]
> $ apt update
> ...
> W: No sandbox user '_apt' on the system, can not drop privileges
> [snip]
> 
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
>  meta/recipes-devtools/apt/apt_1.8.2.1.bb | 24 +++++++++++++++++++++---
>  1 file changed, 21 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/recipes-devtools/apt/apt_1.8.2.1.bb b/meta/recipes-devtools/apt/apt_1.8.2.1.bb
> index de0e150a2e..57bd7ca600 100644
> --- a/meta/recipes-devtools/apt/apt_1.8.2.1.bb
> +++ b/meta/recipes-devtools/apt/apt_1.8.2.1.bb
> @@ -17,6 +17,12 @@ SRC_URI_append_class-native = " \
>             file://0001-Do-not-configure-packages-on-installation.patch \
>             "
>  
> 
> 
> 
> 
> 
> 
> 
> +SRC_URI_append_class-nativesdk = " \
> +           file://0001-Do-not-init-tables-from-dpkg-configuration.patch \
> +           file://0001-Revert-always-run-dpkg-configure-a-at-the-end-of-our.patch \
> +           file://0001-Do-not-configure-packages-on-installation.patch \
> +           "
> +
>  SRC_URI[sha256sum] = "6d447f2e9437ec24e78350b63bb0592bee1f050811d51990b0c783183b0983f8"
>  LIC_FILES_CHKSUM = "file://COPYING.GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>  
> 
> 
> 
> 
> 
> 
> 
> @@ -24,9 +30,12 @@ LIC_FILES_CHKSUM = "file://COPYING.GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>  # so we check the latest upstream from a directory that does get updated
>  UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/a/apt/"
>  
> 
> 
> 
> 
> 
> 
> 
> -inherit cmake perlnative bash-completion upstream-version-is-even
> +inherit cmake perlnative bash-completion upstream-version-is-even useradd
> +
> +USERADD_PACKAGES = "${PN}"
> +USERADD_PARAM_${PN} = "--system --home /nonexistent --no-create-home _apt"
> 

I think meta-selftest/files/static-passwd  will need this adding for
the selftests to pass?

Cheers,

Richard


  reply	other threads:[~2021-01-15 11:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  9:45 [PATCH 1/3] dpkg: add nativesdk support hongxu
2021-01-15  9:45 ` [PATCH 2/3] apt: " hongxu
2021-01-15 11:26   ` Richard Purdie [this message]
     [not found]   ` <165A643B5E417599.21794@lists.openembedded.org>
2021-01-15 16:51     ` [OE-core] " Richard Purdie
2021-01-16  2:49       ` hongxu
2021-01-15  9:45 ` [PATCH 3/3] deb: do not insert feed uris if apt not installed hongxu
2021-01-15 22:21   ` [OE-core] " Richard Purdie
2021-01-16  2:46     ` hongxu
2021-01-16  3:49     ` [PATCH V2] " hongxu
2021-01-15 22:15 ` [OE-core] [PATCH 1/3] dpkg: add nativesdk support Richard Purdie
2021-01-16  2:50   ` hongxu
2021-01-16  3:47   ` [PATCH V2] " hongxu

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=adca85be61ff1fa0f2c4cb0d4a2093daa0d65b48.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=hongxu.jia@windriver.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