Bug 751830
| Summary: | pull selinux policy into subpackage | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Joey Boggs <jboggs> |
| Component: | ovirt-node | Assignee: | Fabian Deutsch <fdeutsch> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | fdeutsch, jboggs, mburns, ovirt-bugs, ovirt-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-node-3.0.3 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-28 11:57:59 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Joey Boggs
2011-11-07 17:35:12 UTC
dwalsh suggested to build the selinux module during build and just install it in %post and pull it completely out of the -post ks script. That's a good reason why we should create the policy subpackage. Mike, is there a reason why the ovirt policy is compiled and installed during post part of the KS file? I wonder if there are any constraints I have to take care of when pulling the policy into a separate package. Moving the module into a subpackage means that we will be building the module at buildtime (which is a good thing IMHO) and that we install it like a regular rpm. No reason I can think of. The following patch pulls out the selinux policy module compilation out of the post KS part into the node build process (actually into the package build process). The policy module is the installed during %install and activated during %post. http://gerrit.ovirt.org/14052 |