[This is a general moan / observation ... Sorry!] SELinux policy is sometimes now split so that packages can carry their own policy subpackage. Examples include:
https://src.fedoraproject.org/rpms/passt/blob/rawhide/f/passt.spec#_36 https://src.fedoraproject.org/rpms/nbdkit/blob/rawhide/f/nbdkit.spec#_751 I've recently been installing a lot of VMs with virt-v2v, and of the approximately 3 minutes spent installing the required packages, I'd estimate that around 2 minutes is spent running the *-selinux post-install scripts for swtpm-seinux, passt-selinux and nbdkit-selinux. For some reason passt-selinux is particularly excessive (I eyeballed it at around 75 seconds). I wonder if there's a way we could have RPM rebuild the SELinux policy just once in this situation? And asking another level of "why", why is rebuilding the policy so slow in the first place? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
