Bug ID | 1198128 |
---|---|
Summary | Optimize NetworkManager subpackages. |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | GNOME |
Assignee | gnome-bugs@suse.de |
Reporter | yfjiang@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
Currently NetworkManager is nearly "monotholically packaged", which appears nearly everything is packed in a single package networkManager (except for libnm, adsl&pppoe were splitted into sub packages). With the NetworkManager's role played in areas like cloud instances and storage-sensitive devices, it is more important to split the package into more fine-grain items so that people could select what to install to precisely fit the requirement. For example, Fedora had a practical package splitting to get the major feautures divided: https://src.fedoraproject.org/rpms/NetworkManager/raw/f36/f/NetworkManager.spec where I think it makes sense to look into those packages: %package bluetooth ... %package team ... %package wifi ... %package wwan ... %package ovs ... %package ppp ... %package config-server ... %package tui ... %package cloud-setup ... Probably we could do things similar.