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