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 16:51:26 +0000 [thread overview]
Message-ID: <fb1e48e9b2cca8a0acb5d9da2081e091620253f2.camel@linuxfoundation.org> (raw)
In-Reply-To: <165A643B5E417599.21794@lists.openembedded.org>
On Fri, 2021-01-15 at 11:26 +0000, Richard Purdie via
lists.openembedded.org wrote:
> On Fri, 2021-01-15 at 17:45 +0800, hongxu wrote:
> >
> >
> > -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?
I've tweaked the patch I've queued in master-next for testing.
I also added a comment here to say why we need this user (it used to
exist but was removed as it wasn't realised what it was for).
Cheers,
Richard
next prev parent reply other threads:[~2021-01-15 16:51 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 ` [OE-core] " Richard Purdie
[not found] ` <165A643B5E417599.21794@lists.openembedded.org>
2021-01-15 16:51 ` Richard Purdie [this message]
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=fb1e48e9b2cca8a0acb5d9da2081e091620253f2.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