>  (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.

From my point of view, if it has Cockpit by default which adds NM, then NM should be there by default - i.e. should not be removed with Cockpit.


Radka
  

Radka Janeková
.NET & OpenShift Engineer, Red Hat
IRC: radka | Freenode: Rhea


On Tue, Oct 17, 2017 at 3:12 PM, Martin Pitt <martin@piware.de> wrote:
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

_______________________________________________
cockpit-devel mailing list -- cockpit-devel@lists.fedorahosted.org
To unsubscribe send an email to cockpit-devel-leave@lists.fedorahosted.org