![]() ![]() Backporting commitsĬommits to policy/modules/contrib needing backport to stable branches will be backported to the legacy contrib repo. ![]() Pull requests which have not been merged yet require the submitter to rebase it and open against the base repo. No change other than where to look for the previous contrib modules and where to submit pull requests. How selinux-policy contributors are affected? in the dist git were updated to use the new location for builds targeting rawhide or f34+. No change for policy writing other than where to look for modules, previously found in the contrib repo. How custom selinux-policy developers are affected? No change for working in the selinux-policy base repo. Selinux-policy-contrib repo are in the selinux-policy base repo, directory Inside the repo: all files previously accessible from the root directory in the There should now be just one notable change It mainly is an internal change of where the git repository is stored and Stable branches ( f33, f32, all older ones) remain unchanged. ![]() ![]() The contrib repo's commit history are a part of the base repo. Now used the corresponding contrib branch was archived and will not be usedĪny longer. When working in the rawhide branch, only the base repo is With SELinux policy repos more difficult.įrom now on, these repos are merged into one, containing sources from both.Īll the changes affect both repos, rawhide branches and future branches Now just a source of confusion and made dealing This division into two repos was merely a historical artifact, being Previously, SELinux policy packages in Fedora used 2 repositories: On November 25th, 2020, the selinux-policy-contrib repository was merged with selinux-policy. This is necessary on chef-client < 12.18.Merging selinux-policy-contrib repository with selinux-policy
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |