All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Arnold <stephen.arnold42@gmail.com>
To: Trevor Woerner <trevor.woerner@linaro.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][MASTER][PATCH] lxdm: add libpam DEPENDS
Date: Tue, 24 Jun 2014 21:16:02 -0700	[thread overview]
Message-ID: <CAOLEWZUbT17s1pxuxK7Tkvvf6Jk2AO2w5dk2iWuAVCfzTkpPsA@mail.gmail.com> (raw)
In-Reply-To: <53A9E471.8080500@linaro.org>

Yeah, it would certainly make more sense with a packageconfig option for
that; currently it doesn't work either with or without the "pam" feature
due to the missing plugins.  So if you want hard deps, then the plugins
need to be included as rdeps.  Otherwise, adding an appropriate
packageconfig option to the flexible depends sounds good.

I still need an init script anyway, so...

Steve


On Tue, Jun 24, 2014 at 1:49 PM, Trevor Woerner <trevor.woerner@linaro.org>
wrote:

> On 06/24/14 16:02, Stephen Arnold wrote:
> > but not as "hard" deps (since pam is an
> > optional feature).
>
> I wasn't 100% before sending that patch, but somehow I assumed it'd be
> best as a:
>
> DEPENDS += "${@base_contains("DISTRO_FEATURES", "pam"...
>
> or some such. But I put it as a hard DEPENDS because lxdm has a
> "--without-pam" configuration option which is not being used, so I
> therefore concluded lxdm always wants pam support.
>


  reply	other threads:[~2014-06-25  4:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 18:26 [meta-oe][MASTER][PATCH] lxdm: add libpam DEPENDS Trevor Woerner
2014-06-24 20:02 ` Stephen Arnold
2014-06-24 20:49   ` Trevor Woerner
2014-06-25  4:16     ` Stephen Arnold [this message]
2014-07-10 15:09       ` Trevor Woerner
2014-07-10 16:35         ` Stephen Arnold
2014-07-14 17:19         ` Stephen Arnold

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=CAOLEWZUbT17s1pxuxK7Tkvvf6Jk2AO2w5dk2iWuAVCfzTkpPsA@mail.gmail.com \
    --to=stephen.arnold42@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=trevor.woerner@linaro.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.