From: Philip Balister <philip@balister.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Bringing an image from OE to OE-Core
Date: Wed, 05 Oct 2011 16:03:13 -0400 [thread overview]
Message-ID: <4E8CB801.7050003@balister.org> (raw)
In-Reply-To: <CAMKF1soVx-m6aa0xhHeSvPDSBQvwc+L37r1xgTs58ZuCs+XhzQ@mail.gmail.com>
On 10/05/2011 03:35 PM, Khem Raj wrote:
> On Wed, Oct 5, 2011 at 7:14 AM, Philip Balister<philip@balister.org> wrote:
>>
>> 1) I do not want rpm in the image. This would confuse my customer base.
>> 2) I am tired of dropbear, I want openssh only.
>> 3) I need the full versions of tools, not the busybox ones.
>> 4) I am not limited to gpv2 software.
>>
>> Richard, it looks to me like we should add an item for the next Yocto
>> development cycle to review how images are built and try to make the base
>> stuff in oe-core more usable by everyone. We need to define what choices are
>> made by distros. For example opkg, rpm, no package management in image.
>> Images may want dropbear or openssh.
>>
>> Short term, I think I'll copy the tasks/images into my bsp and get some
>> stuff together for testing. I'd like a better long term solution though.
>
> There always will be customizations needed. But we can strive for
> better basic blocks
Sure. The immediate things I noticed are rpm being installed and lack of
a way to chose between dropbear/openssh.
I think it is worth having a conversation to find out if when can make
it easier for users to create images, with a small number of knobs to turn.
Philip
next prev parent reply other threads:[~2011-10-05 20:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 19:58 Bringing an image from OE to OE-Core Philip Balister
2011-10-04 20:08 ` Saul Wold
2011-10-04 20:27 ` Philip Balister
2011-10-04 20:32 ` Saul Wold
2011-10-04 22:43 ` Mark Hatle
2011-10-05 14:14 ` Philip Balister
2011-10-05 14:47 ` Eric Bénard
2011-10-05 15:49 ` Mark Hatle
2011-10-05 16:20 ` Koen Kooi
2011-10-05 21:07 ` Philip Balister
2011-10-05 16:39 ` Eric Bénard
2011-10-05 19:35 ` Khem Raj
2011-10-05 20:03 ` Philip Balister [this message]
2011-10-05 20:18 ` Joshua Lock
2011-10-05 20:24 ` Khem Raj
2011-10-05 22:51 ` Saul Wold
2011-10-07 5:51 ` Frans Meulenbroeks
2011-10-04 20:15 ` Khem Raj
2011-10-04 20:27 ` 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=4E8CB801.7050003@balister.org \
--to=philip@balister.org \
--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 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.