From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [thud][PATCH] systemd: RDEPENDS on util-linux-umount
Date: Fri, 8 Mar 2019 12:50:23 +0200 [thread overview]
Message-ID: <20190308105023.GA3056@localhost> (raw)
In-Reply-To: <87265d8970131474709a4589cdef7015fa72b87a.camel@linuxfoundation.org>
On Thu, Mar 07, 2019 at 09:48:02PM +0000, Richard Purdie wrote:
>
> Going from memory I think there were some responses saying we should
> probably add this patch regardless since we already needed util-linux-
> mount. I didn't think it was a huge issue since mount was already there
> and it seemed to solve some problems others were having.
>
> I don't have a strong preference either way, we just need a general
> consensus about what to do...
The general problem seems to be that systemd upstream does not care much
whether busybox versions of commands work with systemd.
This creates a conflict between upstream recommendations and aiming at a
tiny system when using systemd.
The latter would require a continuous effort from someone at OE/Yocto to
ensure that the runtime dependencies of systemd are small but working.
> Cheers,
>
> Richard
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-03-08 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 14:27 [thud][PATCH] systemd: RDEPENDS on util-linux-umount Adrian Bunk
2019-03-07 14:56 ` Leon Woestenberg
2019-03-07 15:18 ` Adrian Bunk
2019-03-07 15:36 ` Leon Woestenberg
2019-03-07 15:38 ` André Draszik
2019-03-07 21:48 ` Richard Purdie
2019-03-08 10:50 ` Adrian Bunk [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=20190308105023.GA3056@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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