On 15-12-16 19:43, Michael Biebl wrote:
Am 15.12.2016 um 19:41 schrieb Michael Biebl:
Control: reassign -1 netbase
Control: retitle -1 Drop/Demote recommends on ifupdown
Am 15.12.2016 um 13:17 schrieb Olliver Schinagl:
Package: systemd
Version: 232-3
Severity: normal
File: systemd-networkd
Dear Maintainer,
currently, when installing a small server, with systemd(-sysv),isc-dhcp-
server,openntpd
it pulls in some dependencies, of which one comes from netbase, which is a
dependancy of openntpd.
While the choice ultimatly is with the user, having systemd-networkd and
systemd-resolved, which covers most basic network needs and in theory supplies
netbase. So should systemd not also thus provide netbase?
If a user wants to install other network tools or packages depend on specific
networking packages, they can list them as such, naturally.
Having systemd Provides: netbase doesn't really make sense. systemd
doesn't provide that functionality after all.
I don't know what netbase does and does not provide, but
systemd-networkd provides pretty much everything you need to setup and
run (quite an advanced) network these days? So what doesn't systemd provide?
You could ask the netbase maintainer, Marco, though, if he was open to
drop the Recommends: ifupdown or demote it to Suggests.
That would seem like a reasonable suggestion to me.
So I'm reassigning this to netbase and let Marco decide.
Keep in mind though, that ifupdown will likely be installed anyway,
since it has Priority: important
Well I installed a container via debootstrap and minbase and only added
isc-dhcp-server. Then I decided I wanted <package> which needs netbase
and only then it started to pull in ifupdown etc.
