Hello all, Stef Walter [2017-10-17 11:48 +0200]: > This is a distro specific packaging/dependency bug and not a bug in Cockpit. > > Stephen, should we file a Fedora bug about this? Any ideas which component?
There is a (slightly political) decision to make first. Based on that, there
are different solutions:
(1) If the *intention* is that Fedora Server should have NM by default, then
this should be added do the explicit list of "top-level packages" that the
OS installer image is built from.
After installing all packages, the installer should mark all these
"top-level" packages as manually installed (dnf mark install), so that
they don't suffer from this automatic cleanup. (This is what the
Debian/Ubuntu installer does, with "apt-mark").
(2) If the intention is that Fedora Server should by default manage its
networking with something else (networkd, or the old sysconfig scripts
or whatnot), as many people don't like NM on their server, then it
shouldn't install cockpit-networkmanager by default either. In that case
we should lower the recommends from the "cockpit" metapackage to
Suggests:.
Martin
signature.asc
Description: PGP signature
_______________________________________________ cockpit-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
