Hello,
aa-status --enabled (and only --enabled AFAIK) is used in dh_apparmor,
which means we have to keep the dependencies as small as possible,
especially "import apparmor.$something".
Needless to say that this makes improving aa-status quite difficult.
We discussed splitting off an "aa-enabled" tool that just does what
aa-status --enabled does with minimal dependencies.
To allow a smooth transition, I propose to add a little aa-enabled tool
to 2.9 and 2.10 which just does
#!/bin/sh
exec aa-status --enabled
This means Debian and Ubuntu can switch dh_apparmor etc. to use
aa-enabled instead of aa-status --enabled _now_ (assuming it fits for
them) instead of having to wait for a major AppArmor release. This
allows a longer migration period.
For trunk, I propose aa-enabled should actually do the work itsself -
see the "Re: [apparmor] [patch] utils: make aa-status(8) function
without python3-apparmor" mail for a proposal.
Regards,
Christian Boltz
--
Und da Du mit der Installation so wenig Probleme hast, könntest Du
doch die gesparte Zeit in ein paar Großbuchstaben investieren. Liest
sich besser am Bildschirm. Danke. [Helga Fischer in suse-linux]
--
AppArmor mailing list
AppArmor@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/apparmor
