> > > Hi Zbyszek, > > > Would it make sense to do the same for systemd-resolved ? > > > Sounds like it has similar impact/scope wrt coreos. > > > > Yes please, I would like this for Edge/IoT too (both network/resolved) > > as there are use cases there where we'd like not to ship these too. > > > > Please, no more package splitting. And NetworkManager is used across > all variants of Fedora, so resolved should be installed in all places > where NetworkManager is used. Both Editions and Spins are allowed to deviate from defaults, like Server uses XFS and Desktops now use btrfs for filesystems. ATM I intended to leave it as it is but I want the option to be able to exclude it, and if it's not in use and we don't ship it means if there's 1000s of systems we don't need to patch if there's a CVE in those components. I think the ability to shrink and not include things not in use is important, that is the whole point of the minimisation objective after all. Peter _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
