On Sep 14, 2012 5:03 PM, "Alex Brandt" <alund...@alunduil.com> wrote:
> Thanks for the wonderful feedback. The way I have things setup now is an selinux directory in my project's source directory. Should I move these to the files directory of an ebuild for this selinux policy? Is it acceptable to store them in the project's source (and by extension tarball)? Are these just the policy sources for the project? If so, then the code should be fairly isolated. So after policy development I think it is wise to try and submit them upstream later. > > I'll take a look at the hardened overlay to model by live ebuilds for this but wanted to make sure I wasn't going down the wrong path. All of the ebuilds I've seen so use the selinux eclass so extensively that it was hard to separate out where things lived upstream to the ebuild. Yes for gentoo the eclass makes it a lot easier to package. However, that has nothing to do with policy development. Wkr Sven
