Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] image.bbclass: depends on virtual/kernel
Date: Mon, 25 Nov 2013 12:57:17 +0000	[thread overview]
Message-ID: <1385384237.24083.4.camel@ted> (raw)
In-Reply-To: <CAP9ODKpZaWs=9zfvN_WmP7g2rRpc70po-Mdd_g75B8=XwDNAhg@mail.gmail.com>

On Mon, 2013-11-25 at 10:28 -0200, Otavio Salvador wrote:
> On Mon, Nov 25, 2013 at 10:09 AM, ChenQi <Qi.Chen@windriver.com> wrote:
> > On 11/23/2013 06:32 AM, Andrea Adami wrote:
> >>
> >> On Fri, Nov 22, 2013 at 8:58 PM, Otavio Salvador
> >> <otavio@ossystems.com.br> wrote:
> >>>
> >>> On Fri, Nov 22, 2013 at 3:39 AM,  <Qi.Chen@windriver.com> wrote:
> >>>>
> >>>> From: Chen Qi <Qi.Chen@windriver.com>
> >>>>
> >>>> Add 'virtual/kernel' to DEPENDS in image.bbclass so that the kernel
> >>>> can get built by default. Otherwise, the kernel will not get built
> >>>> unless it's required by other packages like v86d. As a result, if
> >>>> we build 'core-image-minimal' for qemumips, the kernel is not built,
> >>>> and we have 'bitbake linux-yocto' before we can use runqemu to start
> >>>> the target.
> >>>>
> >>>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> >>>
> >>> If I have a board without modules there's no need to have the depends.
> >>> Why you need this?
> >>>
> >> The first quenstion in my mind when I read the post:
> >>
> >> Odd...wasn't core-image-minimal purposedly lean, mutilated and without
> >> kernel modules ?
> >> (Not that really 'used' it, just booted 'cause was small and could
> >> always fit on nand/nor)
> >
> >
> > What I want to do here is to trigger building of kernel when building out an
> > image. I'm not proposing to make all images have kernel -modules installed.
> 
> Yes but you're proposing *all* images to depends on kernel. This is not a need.
> 
> >> It has always been like this: if one needs the kernel and the modules
> >> can add that in his machine.conf.
> >
> >
> > Previously, the kernel is built out by default because
> > packagegroup-core-boot has a dependency on it. Now the dependency is gone.
> >
> > I'm not talking about installing kernel modules onto images.
> 
> and I am not keen to have all image depending on kernel build. Sorry.
> 
> Nack!

Right now we have a fairly serious regression where the documented use
cases in the manual don't work and people find that behaviours that used
to work no longer do. This is quite damaging.

I'd appreciate working towards a constructive resolution of the
regression, thanks.

Richard





      reply	other threads:[~2013-11-25 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  5:39 [PATCH 0/1] image.bbclass: depends on virtual/kernel Qi.Chen
2013-11-22  5:39 ` [PATCH 1/1] " Qi.Chen
2013-11-22 11:38   ` Martin Jansa
2013-11-22 11:41   ` Phil Blundell
2013-11-22 12:06     ` Richard Purdie
2013-11-22 19:58   ` Otavio Salvador
2013-11-22 22:32     ` Andrea Adami
2013-11-25 12:09       ` ChenQi
2013-11-25 12:28         ` Otavio Salvador
2013-11-25 12:57           ` Richard Purdie [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=1385384237.24083.4.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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