[meta-virtualization] [meta-overc][PATCH] local.conf.sample: set DISTRO

Mark Asselstine mark.asselstine at windriver.com
Thu Oct 29 19:56:40 PDT 2015


Please ignore this one, accidentally got picked up in my send-email expression.

Mark

On Thu, Oct 29, 2015 at 10:54 PM, Mark Asselstine
<mark.asselstine at windriver.com> wrote:
> My builds kept on producing images with sysvinit as the init system
> despite being told that systemd was the expected default throughout
> meta-overc. After poking around I found that the DISTRO in the
> local.conf.sample still had the default DISTRO set to 'poky' so
> changing this to be the expected 'pod'.
>
> Signed-off-by: Mark Asselstine <mark.asselstine at windriver.com>
> ---
>  meta-pod/conf/local.conf.sample | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-pod/conf/local.conf.sample b/meta-pod/conf/local.conf.sample
> index a5f9bfd..dbab304 100644
> --- a/meta-pod/conf/local.conf.sample
> +++ b/meta-pod/conf/local.conf.sample
> @@ -115,7 +115,7 @@ KMACHINE_genericx86-64 ?= "common-pc-64"
>  # Ultimately when creating custom policy, people will likely end up subclassing
>  # these defaults.
>  #
> -DISTRO ?= "poky"
> +DISTRO ?= "pod"
>  # As an example of a subclass there is a "bleeding" edge policy configuration
>  # where many versions are set to the absolute latest code from the upstream
>  # source control systems. This is just mentioned here as an example, its not
> --
> 2.1.4
>
> --
> _______________________________________________
> meta-virtualization mailing list
> meta-virtualization at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-virtualization


More information about the meta-virtualization mailing list