From: Tim Orling <ticotimo@gmail.com>
To: yocto@lists.yoctoproject.org, ruom9900@gmail.com
Subject: Re: [yocto] Adding a group to my local.conf file #kirkstone #poky
Date: Fri, 3 May 2024 12:32:47 -0700 [thread overview]
Message-ID: <CANx9H-AXEBbP3MwQEyWwO=tqoGvgPxMZbtP5yGCFnaJLMoOf5A@mail.gmail.com> (raw)
In-Reply-To: <OKoY.1714760937995886315.iWwX@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
On Fri, May 3, 2024 at 11:29 AM ruom9900 via lists.yoctoproject.org
<ruom9900=gmail.com@lists.yoctoproject.org> wrote:
> Hello,
> Is there any way possible to add a custom group to the local.conf file?
The classic way is with extrausers (kirkstone docs for reference):
https://docs.yoctoproject.org/4.0.17/ref-manual/classes.html#extrausers
This happens at the image level, but individual recipes that need access to
other groups may be a challenge.
There were improvements made in scarthgap, especially the USERADD_DEPENDS
variable:
https://docs.yoctoproject.org/ref-manual/variables.html#term-USERADD_DEPENDS
This allows better handling of users and groups at the recipe level.
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#63029):
> https://lists.yoctoproject.org/g/yocto/message/63029
> Mute This Topic: https://lists.yoctoproject.org/mt/105893984/924729
> Mute #kirkstone:
> https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone
> Mute #poky:https://lists.yoctoproject.org/g/yocto/mutehashtag/poky
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> ticotimo@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
[-- Attachment #2: Type: text/html, Size: 2655 bytes --]
prev parent reply other threads:[~2024-05-03 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 18:28 Adding a group to my local.conf file #kirkstone #poky ruom9900
2024-05-03 19:32 ` Tim Orling [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='CANx9H-AXEBbP3MwQEyWwO=tqoGvgPxMZbtP5yGCFnaJLMoOf5A@mail.gmail.com' \
--to=ticotimo@gmail.com \
--cc=ruom9900@gmail.com \
--cc=yocto@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).