All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Patches and discussions about the oe-core layer"
	<openembedded-core@lists.openembedded.org>
Subject: Re: Core image recipes
Date: Wed, 7 Sep 2011 14:18:10 +0100	[thread overview]
Message-ID: <201109071418.10285.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <201108261739.10025.paul.eggleton@linux.intel.com>

On Friday 26 August 2011 17:39:09 Paul Eggleton wrote:
> On Friday 26 August 2011 17:18:15 Saul Wold wrote:
> > On 08/26/2011 02:47 AM, Paul Eggleton wrote:
> > > meta/recipes-extended/images/core-image-basic.bb
> > 
> > This image should NOT contain any X11, this is supposed to be an
> > extention of core-image-minimal with many of the busybox related
> > commands substituted for the real command set.  The intention of this
> > image is two fold, first it's the largest image that we test against
> > non-GPLv3 and it's the non-graphical LSB image (I am not sure if there
> > is a spec test defined for that.
> 
> Hmm, I'm not sure what I was thinking earlier, you're right it doesn't
> appear to have X. 

Now I know why I thought this. Because task-core.bb defines task packages that 
depend on X applications, any recipe that inherits from core-image will force 
a build of all of the X apps even if it doesn't intend to use them - so both 
core-image-basic and core-image-base suffer from this.  This is not really very 
good and I think we ought to be splitting up task-core to avoid this. FYI 
whilst core-image-minimal inherits from core-image it overrides IMAGE_INSTALL 
and thus doesn't use anything from task-core and therefore does not have this 
issue.

> 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...)
 
> > > Then, we have core-image-base, which whilst it doesn't remove package
> > > management files, does not have "package-management" in its features,
> > > so it's not a whole lot different to core-image-minimal AFAICT.
> > 
> > On this one I might agree, I know that we have not built that image, nor
> > does it seem to be used by anything else.
> 
> 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?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-09-07 13:23 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 [this message]
2011-09-08  3:53       ` Saul Wold
2011-09-08  7:35         ` Paul Eggleton

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=201109071418.10285.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.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 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.