>>>>> Neal Gompa <ngomp...@gmail.com> writes: > The problem is that policy modules can depend on each other, and since > policy modules can add things both to the global store and to the pool > of stuff other modules can use, it has to be processed serially.
Even then, semodule itself takes a surprising amount of time to run. Whether it is faster or slower than the full restorecon run depends quite a bit on how much data the system has. I do wonder if there's any way to make it even a little less glacial. I don't see a way to fully skip any of those steps. Offline updates could skip all but one full restorecon, I suppose. My understanding is that package scriptlets directly call restorecon so if they know everything that needs to be relabeled, they can elect to do so on only a portion of the tree though I don't know how often that applies. -- _______________________________________________ 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
