From: Saul Wold <sgw@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Core image base ssh access and package management
Date: Mon, 17 Dec 2012 09:05:53 -0800 [thread overview]
Message-ID: <50CF50F1.3040102@linux.intel.com> (raw)
In-Reply-To: <50CF38D4.8040701@windriver.com>
On 12/17/2012 07:23 AM, Mark Hatle wrote:
> On 12/17/12 4:48 AM, Alex DAMIAN wrote:
>> From: Alexandru DAMIAN <alexandru.damian@intel.com>
>>
>> Since core-image-base is a default image that developers should
>> use for developing headless applications, it should have
>> package management and ssh access.
>
> I'm not sure I agree with that.
>
> 'base' should be a small system, similar to minimal, but with discrete
> executables. If the user wants packaging and ssh they should be able to
> add it.
>
I agree with Mark on this one.
Sau!
> --Mark
>
>> Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
>> ---
>> meta/recipes-core/images/core-image-base.bb | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-core/images/core-image-base.bb
>> b/meta/recipes-core/images/core-image-base.bb
>> index 8ef3376..a78417f 100644
>> --- a/meta/recipes-core/images/core-image-base.bb
>> +++ b/meta/recipes-core/images/core-image-base.bb
>> @@ -1,7 +1,7 @@
>> DESCRIPTION = "A console-only image that fully supports the target
>> device \
>> hardware."
>>
>> -IMAGE_FEATURES += "splash"
>> +IMAGE_FEATURES += "splash package-management ssh-server-dropbear"
>>
>> LICENSE = "MIT"
>>
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
prev parent reply other threads:[~2012-12-17 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 10:48 [PATCH] Core image base ssh access and package management Alex DAMIAN
2012-12-17 15:23 ` Mark Hatle
2012-12-17 17:05 ` Saul Wold [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=50CF50F1.3040102@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=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