From: Mark Hatle <mark.hatle@windriver.com>
To: <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 12:57:05 -0500 [thread overview]
Message-ID: <5339AC71.4040103@windriver.com> (raw)
In-Reply-To: <CAJTo0LbWk+JrhRJwGVtbUJYBYR4qtmCj+tYy8gTnNAqfByGk_w@mail.gmail.com>
On 3/31/14, 12:31 PM, Burton, Ross wrote:
> On 31 March 2014 18:03, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> I kind of disagree with that, the LSB image can take into account
>> configuration in other parts of the system. If pam isn't configured, I'm
>> not sure that should automatically make it completely unbuildable...
>
> An image that claims to be LSB compliant but due to
> not-immediately-obvious DISTRO_FEATURES isn't actually doesn't seem
> like a good idea to me, fwiw. If the LSB image requires PAM, X11 and
> so on then it should require the features.
I agree the image with the name LSB should enforce the items it knows the LSB
depends on. If the user patches that away then it becomes their issue.
--Mark
> Ross
>
prev parent reply other threads:[~2014-03-31 17:57 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
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 [this message]
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=5339AC71.4040103@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox