[meta-virtualization] [PATCH 2/4] xen: add the ability to configure the name of the policy

[Chris Patterson]

On Thu, Mar 24, 2016 at 11:31 AM, Derek Straka <derek at asterius.io> wrote:
> When using non-release versions, the policy files may have a different name (xenpolicy-${PV}-unstable).  Allow the policy file name to be configured by the xen recipe.
>
> Signed-off-by: Derek Straka <derek at asterius.io>
> ---
>  recipes-extended/xen/xen.inc | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/recipes-extended/xen/xen.inc b/recipes-extended/xen/xen.inc
> index bc5ff85..77740cf 100644
> --- a/recipes-extended/xen/xen.inc
> +++ b/recipes-extended/xen/xen.inc
> @@ -17,6 +17,8 @@ PACKAGECONFIG ??= " \
>      ${@bb.utils.contains('XEN_TARGET_ARCH', 'x86_64', 'hvm', '', d)} \
>      "
>
> +FLASK_POLICY_FILE ?= "xenpolicy-${PV}"
> +
>  PACKAGECONFIG[sdl] = "--enable-sdl,--disable-sdl,virtual/libsdl,"
>  PACKAGECONFIG[xsm] = "--enable-xsmpolicy,--disable-xsmpolicy,checkpolicy-native,"
>  PACKAGECONFIG[systemd] = "--enable-systemd,--disable-systemd,systemd,"
> @@ -343,7 +345,7 @@ FILES_${PN}-devd = "\
>      "
>
>  FILES_${PN}-flask = "\
> -    /boot/xenpolicy-${PV} \
> +    /boot/${FLASK_POLICY_FILE} \

Looks fine to me, but could this just simply be a wildcard (i.e.
/boot/xenpolicy-*)?  Is there a case where it would generate multiple
images and you would want to key off just one?