>> Simply display a splash screen with the remaining steps needed should the >> user want to complete the removal themselves. > I'm not sure this is worth asking the question interactively [...]
Just FYI for anyone wanting to take this up: this is what Debconf priorities are for. If a question needs to be asked only of users poking around, a low-priority Debconf question will still be shown to users that've enabled it. You might also consider showing such detailed information to users that purge the package rather than merely removing it, since they're more likely trying to rid themselves of AppArmor totally. In the other direction, what about maybe doing this the other way around: having the AppArmor userspace package set up some dpkg trigger, prod a change to the initramfs or its sysctl stuff, install a GRUB configuration snippet, or the like, and don't load it in the kernel until this activates it. (Maybe there's something I'm missing; I wonder why this wasn't done when AppArmor became the Debian default.) In other words, we could make loading AppArmor conditional on the userspace utilities, but make the userspace utilities Priority: important so they're still on fresh installs of typical systems. Such an invasive change is probably not good for Trixie though.
signature.asc
Description: This is a digitally signed message part
