[yocto] [meta-selinux][PATCH 1/4] Move common POLICY_* variables to refpolicy_common.inc

Joe MacDonald joe at deserted.net
Wed Oct 30 07:22:08 PDT 2013


[[yocto] [meta-selinux][PATCH 1/4] Move common POLICY_* variables to refpolicy_common.inc] On 13.10.30 (Wed 01:11) Philip Tricca wrote:

> Use default assignment to allow variables to be overriden by recipes
> that include refpolicy_common.inc
> 
> Signed-off-by: Philip Tricca <flihp at twobit.us>
> ---
>  recipes-security/refpolicy/refpolicy_common.inc |   12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/recipes-security/refpolicy/refpolicy_common.inc b/recipes-security/refpolicy/refpolicy_common.inc
> index 0ca0b9d..65d679b 100644
> --- a/recipes-security/refpolicy/refpolicy_common.inc
> +++ b/recipes-security/refpolicy/refpolicy_common.inc
> @@ -24,6 +24,18 @@ inherit autotools pythonnative
>  
>  PARALLEL_MAKE = ""
>  
> +POLICY_NAME ?= "${POLICY_TYPE}"
> +POLICY_DISTRO ?= "redhat"
> +POLICY_UBAC ?= "n"
> +POLICY_UNK_PERMS ?= "allow"
> +POLICY_DIRECT_INITRC ?= "n"
> +POLICY_MONOLITHIC ?= "n"
> +POLICY_CUSTOM_BUILDOPT ?= ""
> +POLICY_QUIET ?= "y"
> +POLICY_MLS_SENS = "16"
> +POLICY_MLS_CATS = "1024"
> +POLICY_MCS_CATS = "1024"

Any reason not to make these last three soft assignments as well?
They're unlikely to change and putting them here makes sense, but I can
also imagine someone wanting to use this as a base for creating a
simplified policy.

-J.

> +
>  EXTRA_OEMAKE += "NAME=${POLICY_NAME} \
>  	TYPE=${POLICY_TYPE} \
>  	DISTRO=${POLICY_DISTRO} \
-- 
-Joe MacDonald.
:wq
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20131030/d27294c5/attachment.pgp>


More information about the yocto mailing list