All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Iorga, Cristian" <cristian.iorga@intel.com>
To: "Iorga, Cristian" <cristian.iorga@intel.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] core-image-lsb: enforce pam as a needed distro feature
Date: Mon, 31 Mar 2014 10:40:01 +0000	[thread overview]
Message-ID: <969F26A8BAB325438E7EB80D3C3134FB1CE75E67@IRSMSX105.ger.corp.intel.com> (raw)
In-Reply-To: <969F26A8BAB325438E7EB80D3C3134FB1CE75DD0@IRSMSX105.ger.corp.intel.com>

Hello,
I have checked, on the autobuilder the right association between LSB-enabled images and proper distro (in our case, poky-lsb) is in place.
As such, my patch should not cause any trouble.
Regards,
Cristian

-----Original Message-----
From: openembedded-core-bounces@lists.openembedded.org [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of Iorga, Cristian
Sent: Monday, March 31, 2014 1:10 PM
To: Richard Purdie
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/1] core-image-lsb: enforce pam as a needed distro feature

No, but I will.

But is this a negative point of the patch, or the autobuilder should be changed?
I acted upon some personal observations, a discussion with Paul (he suggested the change) and also on this guide:
https://wiki.yoctoproject.org/wiki/LSB_Result (in which distro is set to poky-lsb).

Regards,
Cristian

-----Original Message-----
From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
Sent: Monday, March 31, 2014 12:58 PM
To: Iorga, Cristian
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/1] core-image-lsb: enforce pam as a needed distro feature

On Mon, 2014-03-31 at 12:51 +0300, Cristian Iorga wrote:
> core-image-lsb only gave a warning:
> "WARNING: Building libpam but 'pam' isn't in DISTRO_FEATURES, PAM 
> won't work correctly"
> when the proper DISTRO was not set for it.
> default choice would be DISTRO = "poky-lsb", but not necessarily, 
> depending on each custom distro.
> 
> This fix will enforce the proper usage of pam as a distro feature for 
> core-image-lsb by giving an error instead of just a warning.
> 
> Fixes [YOCTO #6073]
> 
> Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
> ---
>  meta/recipes-extended/images/core-image-lsb.bb | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-extended/images/core-image-lsb.bb
> b/meta/recipes-extended/images/core-image-lsb.bb
> index ed316a6..ab61c6e 100644
> --- a/meta/recipes-extended/images/core-image-lsb.bb
> +++ b/meta/recipes-extended/images/core-image-lsb.bb
> @@ -9,4 +9,6 @@ IMAGE_INSTALL = "\
>      packagegroup-core-lsb \
>      "
>  
> -inherit core-image
> +inherit core-image distro_features_check
> +
> +REQUIRED_DISTRO_FEATURES = "pam"


I have a feeling the autobuilder builds core-image-lsb in situations where DISTRO=poky, although I could be wrong. Have you checked?

Cheers,

Richard

--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core


  reply	other threads:[~2014-03-31 10:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31  9:51 [PATCH 0/1] Fix for YB6073 Cristian Iorga
2014-03-31  9:51 ` [PATCH 1/1] core-image-lsb: enforce pam as a needed distro feature Cristian Iorga
2014-03-31  9:58   ` Richard Purdie
2014-03-31 10:09     ` Iorga, Cristian
2014-03-31 10:40       ` Iorga, Cristian [this message]
2014-03-31 11:58     ` Stanacar, StefanX
2014-03-31 12:18       ` Paul Eggleton
2014-03-31 17:03         ` Richard Purdie
2014-03-31 17:23           ` Paul Eggleton
2014-03-31 17:31           ` Burton, Ross
2014-03-31 17:57             ` Mark Hatle

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=969F26A8BAB325438E7EB80D3C3134FB1CE75E67@IRSMSX105.ger.corp.intel.com \
    --to=cristian.iorga@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.