From: Kang Kai <Kai.Kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 02/10] dropbear: Support PAM
Date: Fri, 22 Jul 2011 10:56:50 +0800 [thread overview]
Message-ID: <4E28E6F2.3090303@windriver.com> (raw)
In-Reply-To: <CAMKF1srG7U9508ym_jD-rkoQV_OJ5Ge0Lmd=z0YW-iHgjB9Wqg@mail.gmail.com>
On 2011年07月22日 10:49, Khem Raj wrote:
> On Thu, Jul 21, 2011 at 7:41 PM, Kang Kai<Kai.Kang@windriver.com> wrote:
>> On 2011年07月22日 03:10, Khem Raj wrote:
>>> On Thu, Jul 21, 2011 at 1:54 AM, Koen Kooi<koen@dominion.thruhere.net>
>>> wrote:
>>>> Op 21 jul. 2011, om 10:00 heeft Kang Kai het volgende geschreven:
>>>>
>>>>> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>>>>>
>>>>> I make a patch and some changes in dropbear.inc for supporting pam.
>>>>> - Enable pam in configure
>>>>> - Modify file option.h to open pam supporting
>>>>>
>>>>> Signed-off-by: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>>>>> ---
>>>>> meta/recipes-core/dropbear/dropbear.inc | 6 ++++-
>>>>> .../dropbear/dropbear/dropbear-enable-pam.patch | 21
>>>>> ++++++++++++++++++++
>>>>> 2 files changed, 26 insertions(+), 1 deletions(-)
>>>>> create mode 100644
>>>>> meta/recipes-core/dropbear/dropbear/dropbear-enable-pam.patch
>>>>>
>>>>> diff --git a/meta/recipes-core/dropbear/dropbear.inc
>>>>> b/meta/recipes-core/dropbear/dropbear.inc
>>>>> index 1b51e1a..48cefb6 100644
>>>>> --- a/meta/recipes-core/dropbear/dropbear.inc
>>>>> +++ b/meta/recipes-core/dropbear/dropbear.inc
>>>>> @@ -9,13 +9,15 @@ LIC_FILES_CHKSUM =
>>>>> "file://LICENSE;md5=3a5b0c2f0d0c49dfde9558ae2036683c"
>>>>>
>>>>> DEPENDS = "zlib"
>>>>> RPROVIDES = "ssh sshd"
>>>>> +DEPENDS += "${@base_contains('DISTRO_FEATURES', 'pam', 'libpam', '',
>>>>> d)}"
>>>>>
>>>>> SRC_URI =
>>>>> "http://matt.ucc.asn.au/dropbear/releases/dropbear-${PV}.tar.gz \
>>>>> file://urandom-xauth-changes-to-options.h.patch \
>>>>> file://configure.patch \
>>>>> file://fix-2kb-keys.patch \
>>>>> file://allow-nopw.patch;apply=no \
>>>>> - file://init"
>>>>> + file://init \
>>>>> + file://dropbear-enable-pam.patch "
>>>>>
>>>>> inherit autotools update-rc.d
>>>>>
>>>>> @@ -28,6 +30,8 @@ LD = "${CC}"
>>>>> SBINCOMMANDS = "dropbear dropbearkey dropbearconvert"
>>>>> BINCOMMANDS = "dbclient ssh scp"
>>>>> EXTRA_OEMAKE = 'MULTI=1 SCPPROGRESS=1 PROGRAMS="${SBINCOMMANDS}
>>>>> ${BINCOMMANDS}"'
>>>>> +EXTRA_OECONF += "\
>>>>> + ${@base_contains('DISTRO_FEATURES', 'pam', '--enable-pam',
>>>>> '--disable-pam', d)}"
>>>>>
>>>>> DISTRO_TYPE = "${@base_contains("IMAGE_FEATURES", "debug-tweaks",
>>>>> "debug", "",d)}"
>>>> That one is missing a PR bump
>>> And does this mean that it also needs libpam in DEPENDS ?
>> Yes, I think so. So add the
>>
>> +DEPENDS += "${@base_contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}"
> and to all recipes which are modified
ok, I'll check all the modified recipes.
>
>>
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-07-22 3:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 8:00 [PATCH 00/10] works of adding packages pam support Kang Kai
2011-07-21 8:00 ` [PATCH 01/10] libpam: update to 1.1.4 and add subpackage xtests Kang Kai
2011-07-21 8:00 ` [PATCH 02/10] dropbear: Support PAM Kang Kai
2011-07-21 8:54 ` Koen Kooi
2011-07-21 19:10 ` Khem Raj
2011-07-22 2:41 ` Kang Kai
2011-07-22 2:49 ` Khem Raj
2011-07-22 2:56 ` Kang Kai [this message]
2011-07-21 8:00 ` [PATCH 03/10] openssh: " Kang Kai
2011-07-21 8:55 ` Koen Kooi
2011-07-21 9:05 ` Phil Blundell
2011-07-21 8:00 ` [PATCH 04/10] polkit: " Kang Kai
2011-07-21 8:59 ` Koen Kooi
2011-07-21 9:49 ` Kang Kai
2011-07-21 9:59 ` Koen Kooi
2011-07-22 3:21 ` Kang Kai
2011-07-21 8:00 ` [PATCH 05/10] cups: add pam support Kang Kai
2011-07-21 8:00 ` [PATCH 06/10] screen: " Kang Kai
2011-07-21 8:00 ` [PATCH 07/10] sudo: " Kang Kai
2011-07-21 9:06 ` Phil Blundell
2011-07-21 9:42 ` Kang Kai
2011-07-21 8:00 ` [PATCH 08/10] cronie: enable PAM support for cronie Kang Kai
2011-07-21 8:00 ` [PATCH 09/10] shadow: update pam related configure files Kang Kai
2011-07-21 8:58 ` Koen Kooi
2011-07-22 3:16 ` Kang Kai
2011-07-21 8:00 ` [PATCH 10/10] at: enable pam support Kang Kai
2011-07-21 8:05 ` [PATCH 00/10] works of adding packages " Kang Kai
2011-07-21 8:53 ` Koen Kooi
2011-07-21 9:41 ` Kang Kai
2011-07-21 9:58 ` Koen Kooi
2011-07-21 17:02 ` Saul Wold
2011-07-22 2:18 ` Kang Kai
2011-07-22 3:10 ` Saul Wold
2011-07-22 3:14 ` Kang Kai
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=4E28E6F2.3090303@windriver.com \
--to=kai.kang@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