From: ChenQi <Qi.Chen@windriver.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Peter Marko <peter.marko@siemens.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 0/3] systemd: split timesync and networkd to packages
Date: Wed, 8 Feb 2023 15:53:34 +0800 [thread overview]
Message-ID: <5bc02bfe-29dc-3c8b-5a12-6ae985cf503a@windriver.com> (raw)
In-Reply-To: <CANNYZj-rtpJ51hLGKrFWGkjcGWnn7644eCyHkH+L=hjKRGKrXw@mail.gmail.com>
I think using systemd-conf to solve your original problem is more
reasonable.
After all, the extra rootfs space is very small.
Also, BAD_RECOMMENDATIONS is not supported well for deb package backend.
poky/meta/classes-recipe/rootfs_deb.bbclass: bb.warn("Debian package
install does not support BAD_RECOMMENDATIONS")
Regards,
Qi
On 2/8/23 15:38, Alexander Kanavin wrote:
> On Wed, 8 Feb 2023 at 08:13, Peter Marko <peter.marko@siemens.com> wrote:
>> One alternative we considered was via systemd-conf, but binaries still
>> occupy space in rootfs which is not desirable for some devices:
>> ln -sf /dev/null ${D}${sysconfdir}/systemd/system/systemd-timesyncd.service
> On the other hand it's only a single line of code, instead of doubling
> the ways systemd services can be packaged, chosen via a global,
> publicly documented variable. When you are writing new code paths,
> consider the ever-growing maintenance burden, always, please.
>
> I'm leaning towards installing the services, but not starting them approach.
>
> Alex
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#176893): https://lists.openembedded.org/g/openembedded-core/message/176893
> Mute This Topic: https://lists.openembedded.org/mt/96825676/7304865
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [Qi.Chen@eng.windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
prev parent reply other threads:[~2023-02-08 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 7:12 [OE-core][PATCH 0/3] systemd: split timesync and networkd to packages Peter Marko
2023-02-08 7:12 ` [OE-core][PATCH 1/3] systemd: split timesyncd to its own package Peter Marko
2023-02-08 7:12 ` [OE-core][PATCH 2/3] systemd.bbclass: add non-recursive service packaging Peter Marko
2023-02-08 11:36 ` Peter Kjellerstedt
2023-02-08 12:05 ` adrian.freihofer
2023-02-08 7:12 ` [OE-core][PATCH 3/3] systemd: split networkd to its own package Peter Marko
2023-02-08 7:38 ` [OE-core][PATCH 0/3] systemd: split timesync and networkd to packages Alexander Kanavin
2023-02-08 7:53 ` ChenQi [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=5bc02bfe-29dc-3c8b-5a12-6ae985cf503a@windriver.com \
--to=qi.chen@windriver.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.marko@siemens.com \
/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