https://bugzilla.redhat.com/show_bug.cgi?id=2406130



--- Comment #3 from Neal Gompa <[email protected]> ---
This whole spec probably should be rewritten. Even the openSUSE spec is
slightly bad here.


Initial notes:

* The source package name should be "apparmor", not "libapparmor".
* The python bcond should be dropped, there is no case where it would be
disabled
* We do not follow openSUSE SLPP, so the library subpackage would be
"libapparmor"
* Group tag lines need to be deleted
* Zypp-specific weird split Provides need to be deleted
* Subpackage interdependencies need to be tightened to "=
%{version}-%{release}" rather than the weaker "= %{version}"
* Superfluous Requires on python3 should be dropped


Additionally, I'm pretty sure the apparmor source package provides quite a lot
more than just libapparmor, you should endeavor to build out everything from
the source package that you can.


However, let me address this one point:

> Moreover, once LSM stacking becomes available in the kernel, it would also be 
> useful to allow AppArmor and SELinux to be used simultaneously.

It is extremely unlikely we will enable AppArmor in Fedora for LSM stacking.
Getting the policies to work properly with both will be a nightmare and it is
not worth the pain.


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2406130

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202406130%23c3

-- 
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to