From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: "Eric Le Bihan" <eric.le.bihan.dev@free.fr>,
"Michał Łyszczek" <michal.lyszczek@bofc.pl>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/4] package/openrc: add merged user support
Date: Mon, 9 Oct 2023 17:00:43 +0200 [thread overview]
Message-ID: <20231009150042.GB14234@scaer> (raw)
In-Reply-To: <20231009142915.1775087-4-adam.duskett@amarulasolutions.com>
Adam, All,
On 2023-10-09 16:29 +0200, Adam Duskett spake thusly:
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
> ---
> package/openrc/openrc.mk | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/package/openrc/openrc.mk b/package/openrc/openrc.mk
> index 80a9dec778..c80342a174 100644
> --- a/package/openrc/openrc.mk
> +++ b/package/openrc/openrc.mk
> @@ -37,6 +37,12 @@ else
> OPENRC_CONF_OPTS += -Dpam=false
> endif
>
> +ifeq ($(BR2_ROOTFS_MERGED_USR),y)
> +OPENRC_CONF_OPTS += -Dsplit-usr=true
So, if the user requested a merged usr, you instruct openrc to use a
split usr, ...
> +else
> +OPENRC_CONF_OPTS += -Dsplit-usr=false
... and conversely?
We need a runtime test to validate those two conditions.
Regards,
Yann E. MORIN.
> +endif
> +
> ifeq ($(BR2_PACKAGE_KBD),)
> # keymaps and save-keymaps require kbd_mode and dumpkeys, respectively, so
> # remove them if the kbd package is not selected (e.g. devices with serial
> --
> 2.41.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-09 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 14:29 [Buildroot] [PATCH 1/4] package/openrc: bump version to 0.50 Adam Duskett
2023-10-09 14:29 ` [Buildroot] [PATCH 2/4] package/openrc: add linux-pam support Adam Duskett
2023-10-09 14:29 ` [Buildroot] [PATCH 3/4] package/openrc: add bash-completion support Adam Duskett
2023-10-09 14:29 ` [Buildroot] [PATCH 4/4] package/openrc: add merged user support Adam Duskett
2023-10-09 15:00 ` Yann E. MORIN [this message]
2023-10-09 14:58 ` [Buildroot] [PATCH 1/4] package/openrc: bump version to 0.50 Yann E. MORIN
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=20231009150042.GB14234@scaer \
--to=yann.morin.1998@free.fr \
--cc=adam.duskett@amarulasolutions.com \
--cc=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=michal.lyszczek@bofc.pl \
/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.