Fedora minimal installations
zbyszek at in.waw.pl
Wed Jul 29 14:09:02 UTC 2015
On Wed, Jul 29, 2015 at 03:42:28PM +0200, Harald Hoyer wrote:
> 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):
> So, if we start with systemd, then we'll get 112 packages at least for rawhide.
> systemd (112 pkgs):
> systemd+kernel+grub2+grub2-efi+grubby+dracut (142 pkgs):
> systemd+kernel+grub2+grub2-efi+grubby+dracut+dnf (177 pkgs):
> For a visualization I created some graphs for the systemd only dependencies:
> and a reduced graph, which only displays one dep:
> 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?
That's a package with three directories... Guidelines require this dependency.
> - info - do we really require that for every package, that ships info pages?
This could be converted to a scheme where info (install-info precisely speaking)
is not required, and is only called if it is present. And the info package
would have to install all pre-exisiting info pages upon installation.
(Something like this is done with gtk-update-icon-cache .)
info.rpm is rather small, so I doubt that this is worth the effort.
> - krb5-libs requires gawk - why do libs require utils other than ldconfig?
> - same with device-mapper-libs requiring device-mapper
> - chkconfig - really?
As long as systemd supports sysvinit scripts, this will be required.
More information about the devel