On Thu, Oct 01, 2020 at 11:05:18AM +0200, Petr Menšík wrote:
On 9/30/20 10:36 PM, Zbigniew Jędrzejewski-Szmek wrote:
> On Wed, Sep 30, 2020 at 02:21:19PM -0400, Paul Wouters wrote:
>> On Wed, 30 Sep 2020, Zbigniew Jędrzejewski-Szmek wrote:
>>
>>> the systemd package is getting a systemd-networkd subpackage split out
>>> that will contain systemd-networkd, networkctl, and the associated data
files.
>>> This was requested by coreos maintainers: NetworkManager is used and
skipping
>>> systemd-networkd allows the installation footprint and potential user
confusion
>>> to be reduced a bit. (By 1.6 MB and an unknown amount, respectively.)
>>
>>> The main systemd systemd package Obsoletes the -standalone- packages, so it
>>> should smoothly replace them whenever it is pulled in.
>>
>> In which package will systemd-resolved be?
>
> Still in the main rpm. I don't see a good reason to split it out. It
> can be installed without being enabled (*). And with it being enabled by default
> in F33, there's even less reason to do so. networkd is a few times larger and
> likely to grow (we're adding support for new tunnel types, new protocols,
> and new features all the time. systemd-resolved shouldn't grow too much
> beyond current size.)
Why is it important to require resolved in main package?
See the extensive replies from Neal Gompa in the other part of the thread.
Each split brings a maintenance cost and cognitive overhead for users.
So the question is always "why should we split this out", and not "why
shouldn't we"?
Even for the -networkd it's almost a wash. We split it out to undo a
long-standing problem in coreos. Without that preexisting history [1],
it wouldn't have been split out. Thankfully we don't have a similar situation
with resolved.
It contains
both daemon and lookup tool, couple of bash completion scripts and
manual pages. Reason to split it out was stated already: some people
won't be using it. It is not so small, 650k deserves own package IMHO.
It's a judgment call. Apart from the problems mentioned above, since
it is a default in F33+ now, after splitting it out we'd need to make
sure that it is almost always pulled in. Sorry, no, that's too much fragility
to save <1MB.
Zbyszek
[1]
https://github.com/coreos/fedora-coreos-config/pull/574