"In other words, we have a rather serious catch-22: the policy mechanism is so expensive to reconfigure that it prevents us from adding new features to services. Obviously, that's bad."
Note, the current process isn't always 'no'! :) At a minimum, you'd see this when the image moves to a 16.04 base since we need a policy recompile anyway, but the process for normal OTAs is that the Touch release team makes the call on if it is worth it. If it isn't this time, perhaps your next feature combined with this one is. If not, perhaps batched with other policy updates. What I'm getting at is even now it is a conversation, not unyielding dictum. "If this isn't possible, at least showing a progress indicator during the boot instead of a black screen would make a huge difference. I think the problem isn't necessarily that things are slow, but that there is absolutely no feedback." This isn't possible due to when the compiles must happen relative to when the screen that would provide the feedback comes up. "Could we maybe do the compilation at the end of the upgrade process, before the restart? At that point, we still can do progress indicators and, because the user expects upgrades to be slow, the experience would be better that way." That is what I suggest in the description. The phone team needs to allocate resources to it (and the security team can help guide as needed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350598 Title: AppArmor policy compile improvements To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1350598/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
