Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Core image base ssh access and package management
Date: Mon, 17 Dec 2012 09:23:00 -0600	[thread overview]
Message-ID: <50CF38D4.8040701@windriver.com> (raw)
In-Reply-To: <1355741287-8655-1-git-send-email-alexandru.damian@intel.com>

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.

--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"
>
>




  reply	other threads:[~2012-12-17 15:37 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 [this message]
2012-12-17 17:05   ` Saul Wold

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=50CF38D4.8040701@windriver.com \
    --to=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