[yocto] [oe] meta-selinux

[Joe MacDonald]

[Re: [oe] meta-selinux] On 15.02.11 (Wed 11:55) dpquigl wrote:

> On Wed, 2015-02-11 at 16:29 +0000, Paul Eggleton wrote:
> > (Adding yocto at yoctoproject.org to CC since that is where meta-selinux patches 
> > tend to go at least)
> > 
> > On Wednesday 11 February 2015 10:53:03 dpquigl wrote:
> > > I'm working on OpenXT and it makes use of the meta-selinux repo hosted
> > > by the yocto project. I'm trying to use it with a base openembedded core
> > > and its not in sync with oe-core because its based on pokey. 
> > 
> > To be clear, poky and OE-Core are in lock-step. No patch to core recipes goes 
> > into Poky directly, they are applied to OE-Core and then they flow into Poky 
> > immediately thereafter (Richard, who does the merging of patches into OE-Core, 
> > does the sync to Poky immediately afterwards.)
> > 
> > What's more likely happening I suspect is that you are on a newer 
> > branch/revision of OE-Core/Poky than the meta-selinux maintainers have tested. 
> > I can't speak to the maintenance schedule for meta-selinux but maybe others 
> > with knowledge there can chime in.
> 
> 
> I think this makes the most sense. 3 of the problems were bbappend files
> trying to append the wrong version of a recipe (although with these
> changes I should move them over to a wildcard) and the last one was with
> LXC. After that I encountered a typo in one of the recipes where it
> wasn't able to pull the sources down. 

I merged a set of patches just in the last couple of days that addresses
a SRC_URI issue and wildcards for bbappends that I hope resolves all of
the current crop of these.  If you update your tree now you will likely
see those go away.  If not, please let me know.

Alternatively, I'm not aware of any issues in 1.7 of that sort (though
now that I think about it, I need to check the SRC_URI one, I bet that's
there), so using the latest released Yocto with a like-named branch in
meta-selinux should always be safe.

-J.

> > > This made me think of two questions. 1) Why is this not in OE core since so
> > > many packages in core can potentially have SELinux support enabled and 2) if
> > > its not supposed to be in core where should turning on SELinux support
> > > in a recipe go? For example coreutils can have SELinux support enabled.
> > > Currently this is in meta-selinux as a bbappend to the coreutils
> > > package. This works out because its always going to be there. However
> > > there is also a bbappend for an LXC recipe. LXC isn't in core which
> > > means it has a dependency on a layer not in core.
> > > 
> > > Ideally I would put the recipes needed for SELinux support in core and
> > > have a distro feature which is checked in the recipes in core for
> > > whether or not to add --with-selinux to the build flags. Then LXC could
> > > check a core distro feature and enable SELinux if it wants to.
> > 
> > We have to draw the line somewhere for what to include in OE-Core, and at the 
> > moment I guess we have considered SELinux to be outside its scope. Obviously 
> > these things get re-evaluated from time to time, and SELinux is a little bit 
> > painful for this because of how many recipes it has to touch. Ultimately it 
> > depends on how many people in the embedded space want to enable and use 
> > SELinux.
> > 
> > Thoughts from others?
> > 
> 
> In OpenXT we're using OE to generate images for dom0, a user interface
> domain, a network driver domain, and various other service domains for
> isolating tasks in the platform. In addition to that we're using
> openembedded for building on various embedded research platforms. I'm
> assuming yocto is using SELinux to some extent since they are
> maintaining the repository for it and there are quite a few developers
> using SELiunx on embedded products in Japan.
> 
> 
> Dave
> 
> 
> 
-- 
-Joe MacDonald.
:wq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20150211/168f51ee/attachment.pgp>