From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Core image recipes
Date: Thu, 8 Sep 2011 08:35:50 +0100 [thread overview]
Message-ID: <201109080835.50416.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <4E683C38.20506@linux.intel.com>
On Thursday 08 September 2011 04:53:28 you wrote:
> Now I understand what you are talking about, it might best to split this
> into 2 tasks a task-core moved to recipes-core/tasks and a
> task-core-x11, what about that?
I think that's the only way this can really work, yes.
> >> I can't access the LSB specs website right now
> >> unfortunately but does this have an official name within LSB? It's not
> >> "LSB-Core" is it?
> >
> > Yep, it's LSB-Core (yet another meaning of "core", sigh...)
>
> We could rename basic to task-lsb-core if that's what your thinking, but
> as you point out yet another "core".
Then again, if you're talking about LSB it makes sense to use the correct
terminology.
> >> If there's demand for a minimal image with package management (someone
> >> asked for this on IRC just the other day, and it makes sense to me at
> >> least) then that's what I'd suggest turning this into. In which case it
> >> ought to be called core-image-minimal-pkgmgmt or something similar.
> >
> > Any opinions on this one?
>
> I think this is one that they can create themselves it's would be distro
> specific and would require additional space allocated to the rootfs,
> best for the distro do. Remember we are trying to provide foundations
> and examples. core-image-minimal is supposed to be the smallest possible
> image with login and shell. It can be used by someone to build on.
That's exactly what I am thinking about. Since we already have such an image
(core-image-base) that isn't being used for anything else, why not make it
into something useful? Right now since core-image-minimal overrides
IMAGE_INSTALL you can't use IMAGE_FEATURES and POKY_EXTRA_INSTALL to extend
it, nor does it have package management that some users would be expecting; I
think it would be useful to have a base image where those mechanisms do work.
(Maybe the term "minimal" wouldn't apply to this image.)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-09-08 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 9:47 Core image recipes Paul Eggleton
2011-08-26 16:18 ` Saul Wold
2011-08-26 16:39 ` Paul Eggleton
2011-09-07 13:18 ` Paul Eggleton
2011-09-08 3:53 ` Saul Wold
2011-09-08 7:35 ` Paul Eggleton [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=201109080835.50416.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.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 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.