On Tuesday, September 11, 2012 9:29:42 PM Sven Vermeulen wrote: Depends on the complexity. If you can manage the personal policies as additional files without patching the existing policies then I would use separate files. Recently you can keep those in the ebuilds if you want. Hey Sven,
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)? 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. Thanks again Sven. Regards, -- Alex Brandt Sales Engineer for Rackspace, RHCE http://www.alunduil.com
signature.asc
Description: This is a digitally signed message part.
