In order to define the Base WG core package group and minimize minimal installations for e.g. cloud images and the atomic spin, I created some dependency lists: There are so many definitions of minimum sets: systemd: container boot systemd + bash + login: container boot with login systemd + kernel + bootloader + dracut: machine boot systemd + ... + sshd + firewalld: network minimal Here is a little script to generate the filelist (which apparently is extended by dnf and kickstart with other default packages): <https://harald.fedorapeople.org/pkgset/pkgset.sh> So, if we start with systemd, then we'll get 112 packages at least for rawhide. systemd (112 pkgs): <https://harald.fedorapeople.org/pkgset/f24-systemd-requires.txt> systemd+kernel+grub2+grub2-efi+grubby+dracut (142 pkgs): <https://harald.fedorapeople.org/pkgset/f24-systemd-kernel-requires.txt> systemd+kernel+grub2+grub2-efi+grubby+dracut+dnf (177 pkgs): https://harald.fedorapeople.org/pkgset/f24-systemd-kernel-dnf-requires.txt For a visualization I created some graphs for the systemd only dependencies: <https://harald.fedorapeople.org/pkgset/systemd-all.svg> and a reduced graph, which only displays one dep: <https://harald.fedorapeople.org/pkgset/systemd.svg> A couple of strange deps: - libsemanage requires python (filed as <https://bugzilla.redhat.com/show_bug.cgi?id=1248002>) - emacs-filesystem - do we really need that? - info - do we really require that for every package, that ships info pages? - krb5-libs requires gawk - why do libs require utils other than ldconfig? - same with device-mapper-libs requiring device-mapper - chkconfig - really? please add your findings and/or file bugs -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
