From: Andreas Oberritter <obi@opendreambox.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 2/2] samba, openwsman, pam-ssh-agent-auth, sblim-sfcb, passwdqc, python-pam, smbnetfs: require pam in DISTRO_FEATURES
Date: Fri, 2 Feb 2018 08:46:46 +0100 [thread overview]
Message-ID: <20180202084646.32bbade3@t460p> (raw)
In-Reply-To: <CA+chaQeDFexQPwNj8o4PS2zKqjsbwHBgdqhdDjBx2gxuiHDyow@mail.gmail.com>
Hi Martin,
On Thu, 1 Feb 2018 17:07:55 +0100
Martin Jansa <martin.jansa@gmail.com> wrote:
> Hi Andreas,
>
> I'm just trying to get rid of libpam from builds without pam in
> DISTRO_FEATURES (even for world builds, see the change for oe-core).
>
> I'm aware that libpam usage from samba is a bit strange as discussed few
> times:
> http://lists.openembedded.org/pipermail/openembedded-commits/2016-October/198752.html
> http://lists.openembedded.org/pipermail/openembedded-devel/2016-March/106583.html
> http://lists.openembedded.org/pipermail/openembedded-devel/2016-September/109143.html
>
> Now RSS and also with libpam being available only when pam is in
> DISTRO_FEATURES, we might possibly return the PACKAGECONFIG without
> re-introducing undeterministic link with libpam, but I'm not using samba
> (other than building it in bitbake world) so I'll let that to people who
> actually care about samba itself (and can properly test it in runtime).
I see. Somebody can revert fb5967aaff1a7ee6b5508269735ce2f1b1a7e020 later.
Regards,
Andreas
prev parent reply other threads:[~2018-02-02 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 14:23 [meta-oe][PATCH 1/2] zsh: fix base_bindir installation Martin Jansa
2018-02-01 14:23 ` [meta-oe][PATCH 2/2] samba, openwsman, pam-ssh-agent-auth, sblim-sfcb, passwdqc, python-pam, smbnetfs: require pam in DISTRO_FEATURES Martin Jansa
2018-02-01 15:57 ` Andreas Oberritter
2018-02-01 16:07 ` Martin Jansa
2018-02-02 7:46 ` Andreas Oberritter [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=20180202084646.32bbade3@t460p \
--to=obi@opendreambox.org \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@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 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.