-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/17/2015 06:17 PM, Dan Williams wrote: > On Mon, 2015-11-16 at 20:39 -0500, Stephen Gallagher wrote: >> b'NetworkManager': 138 > > NM does have a larger dep-chain than we'd like, however we did > split the package apart a couple releases ago and made sure that > WWAN, WiFi, and Bluetooth were no longer required for the server > cases. Could you confirm what NetworkManager-* packages are > installed on F23 server? > > The largest deps should be mostly glib2, systemd/udev, NSS, and > D-Bus, all of which should already be on a server install. We'd > love to see if anything unexpected snuck into the dep chain. It was actually included in the tarball I sent in the original email, but: NetworkManager-libnm-1.0.6-6.fc23.x86_64 NetworkManager-1.0.6-6.fc23.x86_64 Yeah, I think NetworkManager is probably fine. It doesn't appear to be using any packages that aren't also used by many other projects. I need to figure out some better metrics for tracking this stuff down. NM definitely requires a lot of packages, but it seems obvious that the problem is deeper in the stack. Some package further back probably has a large number of dependencies. I just spent a little time tracing the dependency chain down and it looks like it's getting most of the chain from dbus->systemd->cryptsetup-libs->device-mapper-libs (at this point the dependencies hit a cycle with systemd...) The next largest dependency chain is with util-linux which appears to depend on a large number of small storage-related and low-level tools. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZMgE4ACgkQeiVVYja6o6PvOgCdEEY/wo0tthiGsKEoGsiOiAnE JkMAn3Na9pXFEeGMU8dMl+3RHQlGe/pt =ff6V -----END PGP SIGNATURE----- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
