All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Tricca <flihp@twobit.us>
To: yocto@yoctoproject.org
Subject: Re: [meta-selinux] Stage SELinux config file in the sysroot.
Date: Mon, 23 Sep 2013 00:25:33 -0400	[thread overview]
Message-ID: <523FC2BD.5050905@twobit.us> (raw)
In-Reply-To: <20130923035119.GA17078@longhaul.twobit.us>

Cc'ing Mark.

On 09/22/2013 11:51 PM, Philip Tricca wrote:
> This is needed to build policy modules outside of the refpolicy.
> Policy module build systems need to determine the name of the policy
> that will be in effect on the target host. This allows them to
> locate the policy headers that will be under
> $sysroot/usr/share/selinux/$name/include. Given that there *could*
> be more than one policy installed in the sysroot we can't assume
> that the policy installed there is the only policy to build against.
> 
> Signed-off-by: Philip Tricca <flihp@twobit.us>
> ---
>  recipes-security/selinux/selinux-config_0.1.bb |    3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/recipes-security/selinux/selinux-config_0.1.bb b/recipes-security/selinux/selinux-config_0.1.bb
> index 9521dcf..ad0d647 100644
> --- a/recipes-security/selinux/selinux-config_0.1.bb
> +++ b/recipes-security/selinux/selinux-config_0.1.bb
> @@ -43,3 +43,6 @@ SELINUXTYPE=${DEFAULT_POLICY}
>  	install -m 0644 ${WORKDIR}/config ${D}/${sysconfdir}/selinux/
>  }
>  
> +sysroot_stage_all_append () {
> +	sysroot_stage_dir ${D}${sysconfdir} ${SYSROOT_DESTDIR}${sysconfdir}
> +}
> 



  reply	other threads:[~2013-09-23  4:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23  3:51 [meta-selinux] Stage SELinux config file in the sysroot Philip Tricca
2013-09-23  4:25 ` Philip Tricca [this message]
2013-09-27 17:55 ` Joe MacDonald

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=523FC2BD.5050905@twobit.us \
    --to=flihp@twobit.us \
    --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.