All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Jie (Jackie)" <Jackie.Huang@windriver.com>
To: Joe MacDonald <Joe_MacDonald@mentor.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [meta-selinux][PATCH] systemd: no need to inherit enable-selinux
Date: Mon, 8 May 2017 01:40:07 +0000	[thread overview]
Message-ID: <1B858668EC6A94408DCA5225FDFA85AA014B76380D@ALA-MBC.corp.ad.wrs.com> (raw)
In-Reply-To: <20170502131344.GD10652@mentor.com>



> -----Original Message-----
> From: Joe MacDonald [mailto:Joe_MacDonald@mentor.com]
> Sent: Tuesday, May 02, 2017 21:14
> To: Huang, Jie (Jackie)
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-
> selinux
> 
> [[yocto] [meta-selinux][PATCH] systemd: no need to inherit enable-selinux] On
> 17.02.22 (Wed 14:44) jackie.huang@windriver.com wrote:
> 
> > From: Jackie Huang <jackie.huang@windriver.com>
> >
> > The selinux PACKAGECONFIG is properly handled in
> > the recipe in oe-core, no need to inherit the
> > enable-selinux bbclass.
> 
> That might be true, but other than belt-and-suspenders, what's the
> harm in this being in the recipe?  I don't necessarily think it's an
> invalid change but my quick count shows ~44 instances of 'inherit
> enable-selinux' and 'inherit with-selinux' in meta-selinux, why's this
> one significant?

That's because I have a patch to change the PACKAGECONFIG for selinux
in oe-core to fix a dependency issue:

-PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux"
+PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux,initscripts-sushell"

But it would be overrode by the one in enable-selinux.bbclass:
$ grep PACKAGECONFIG enable-selinux.bbclass
PACKAGECONFIG_append = " ${@target_selinux(d)}"
PACKAGECONFIG[selinux] = "--enable-selinux,--disable-selinux,libselinux,"

So I need to remove the inherit here in meta-selinux.

Thanks,
Jackie

> 
> -J.
> 
> >
> > Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
> > ---
> >  recipes-core/systemd/systemd_%.bbappend | 1 -
> >  1 file changed, 1 deletion(-)
> >
> > diff --git a/recipes-core/systemd/systemd_%.bbappend b/recipes-
> core/systemd/systemd_%.bbappend
> > index 8d9029b..f1bdaf8 100644
> > --- a/recipes-core/systemd/systemd_%.bbappend
> > +++ b/recipes-core/systemd/systemd_%.bbappend
> > @@ -1,2 +1 @@
> >  inherit enable-audit
> > -inherit enable-selinux
> > --
> > 2.8.3
> >
> --
> -Joe MacDonald.
> :wq


  reply	other threads:[~2017-05-08  1:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-22  6:44 [meta-selinux][PATCH] systemd: no need to inherit enable-selinux jackie.huang
2017-04-18  8:20 ` Huang, Jie (Jackie)
2017-05-02 13:13 ` Joe MacDonald
2017-05-08  1:40   ` Huang, Jie (Jackie) [this message]
2017-05-16 11:54     ` Joe MacDonald
2017-05-17  1:40       ` Huang, Jie (Jackie)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1B858668EC6A94408DCA5225FDFA85AA014B76380D@ALA-MBC.corp.ad.wrs.com \
    --to=jackie.huang@windriver.com \
    --cc=Joe_MacDonald@mentor.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.