> Note, the current process isn't always 'no'! :) Sure, I understand. But, even if the answer is "no" only some of the time, it still means that the apparmor profiles interfere with our normal development process. If I can't add a DBus method when I feel like it, that's a pain. And, depending on how features interact with each other, delaying this may, in turn delay something else, or otherwise make progress more complicated.
Basically, what I'm suggesting is that, if we have a tool that interferes with development, then it is the tool that should change, not the development process. Anyway, I think we've thoroughly canvassed the issue by now :-) If it's possible to move compilation to the end of the upgrade process while the old image is still running, let's do it please! -- 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
