From: Scott Garman <scott.a.garman@intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: "Purdie, Richard" <richard.purdie@intel.com>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 2/7] task-poky-ssh-dropbear: new task recipe for dropbear ssh
Date: Wed, 16 Mar 2011 01:35:36 -0700 [thread overview]
Message-ID: <4D807658.5070600@intel.com> (raw)
In-Reply-To: <5B279E08-1255-421A-82AE-F3795325744B@dominion.thruhere.net>
On 03/16/2011 01:13 AM, Koen Kooi wrote:
>
> Op 16 mrt 2011, om 00:12 heeft Scott Garman het volgende geschreven:
>
>> From: Scott Garman<scott.a.garman@intel.com>
>>
>> This task can be used when IMAGE_FEATURES is set to
>> ssh-server-dropbear.
>>
>> Signed-off-by: Scott Garman<scott.a.garman@intel.com>
>> ---
>> meta/recipes-core/tasks/task-poky-ssh-dropbear.bb | 17 +++++++++++++++++
>> 1 files changed, 17 insertions(+), 0 deletions(-)
>> create mode 100644 meta/recipes-core/tasks/task-poky-ssh-dropbear.bb
>>
>> diff --git a/meta/recipes-core/tasks/task-poky-ssh-dropbear.bb b/meta/recipes-core/tasks/task-poky-ssh-dropbear.bb
>> new file mode 100644
>> index 0000000..870d2d9
>> --- /dev/null
>> +++ b/meta/recipes-core/tasks/task-poky-ssh-dropbear.bb
>> @@ -0,0 +1,17 @@
>> +DESCRIPTION = "Dropbear SSH task for Poky"
>> +LICENSE = "MIT"
>> +LIC_FILES_CHKSUM = "file://${POKYBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 \
>> + file://${POKYBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
>> +PR = "r0"
>> +
>> +PACKAGES = "\
>> + task-poky-ssh-dropbear \
>> + task-poky-ssh-dropbear-dbg \
>> + task-poky-ssh-dropbear-dev \
>> + "
>> +
>> +ALLOW_EMPTY = "1"
>> +
>> +RDEPENDS_task-poky-ssh-dropbear = "dropbear"
>> +RDEPENDS_task-poky-ssh-dropbear-dbg = "dropbear-dbg"
>> +RDEPENDS_task-poky-ssh-dropbear-dev = "dropbear-dev"
>
> looks like a good candidate for 'inherit task'
Thanks for the suggestion, Koen.
Richard - a quick browse through Poky's tasks shows only one of them
uses inherit task (task-base.bb). Is there any reason to avoid this that
I'm not aware of? Otherwise, I'm happy to do a respin with inherit task.
Thanks,
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-03-16 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 23:11 [PATCH 0/7] Set ssh server using IMAGE_FEATURES, v3 Scott Garman
2011-03-15 23:12 ` [PATCH 1/7] task-base, task-poky-basic, task-poky: Remove hard-coded references to dropbear Scott Garman
2011-03-15 23:12 ` [PATCH 2/7] task-poky-ssh-dropbear: new task recipe for dropbear ssh Scott Garman
2011-03-16 8:13 ` Koen Kooi
2011-03-16 8:35 ` Scott Garman [this message]
2011-03-16 13:34 ` Richard Purdie
2011-03-15 23:12 ` [PATCH 3/7] task-poky-ssh-openssh: new task recipe for openssh ssh Scott Garman
2011-03-16 8:14 ` Koen Kooi
2011-03-15 23:12 ` [PATCH 4/7] poky-image.bbclass: add new IMAGE_FEATURES for ssh servers Scott Garman
2011-03-15 23:12 ` [PATCH 5/7] poky-image.bbclass: add ssh-server-dropbear to SATO_IMAGE_FEATURES Scott Garman
2011-03-15 23:12 ` [PATCH 6/7] poky-image-lsb: add ssh-server-openssh to IMAGE_FEATURES Scott Garman
2011-03-15 23:12 ` [PATCH 7/7] poky-image-basic: " Scott Garman
2011-03-16 13:43 ` [PATCH 0/7] Set ssh server using IMAGE_FEATURES, v3 Richard Purdie
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=4D807658.5070600@intel.com \
--to=scott.a.garman@intel.com \
--cc=koen@dominion.thruhere.net \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@intel.com \
/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