Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Martin Hundebøll" <mnhu@prevas.dk>,
	"Paul Barker" <pbarker@toganlabs.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] kernel-module-split: rrecommend kernel-image instead of rdepend
Date: Mon, 11 Sep 2017 13:50:51 +0100	[thread overview]
Message-ID: <1505134251.18640.2.camel@linuxfoundation.org> (raw)
In-Reply-To: <a52ee58f-6ede-006d-750a-38b5d5f59b8a@prevas.dk>

On Mon, 2017-09-11 at 14:19 +0200, Martin Hundebøll wrote:
> 
> On 2017-09-11 11:26, Richard Purdie wrote:
> > 
> > On Mon, 2017-09-11 at 09:02 +0200, Martin Hundebøll wrote:
> > > 
> > > Reverting the patch is fine by me - sorry for the noise.
> > Are you sure? I can't imagine being able to influence this at all
> > from
> > an image recipe, either the dependency is present or its not and it
> > would be set from the global configuration, not from an image
> > recipe...
> Pretty sure, yes.
> 
> conf/distro/basic.conf:
> RDEPENDS_kernel-base = ""
> 
> recipes-filesystems/rootfs.bb:
> IMAGE_INSTALL += "kernel-image kernel-module-foo"
> 
> recipes-filesystems/rescuefs.bb:
> IMAGE_INSTALL += "kernel-module-foo"

Now I understand, I thought you meant adding in the RRECOMMENDS from an
image recipe.

Thanks,

Richard


      reply	other threads:[~2017-09-11 12:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-21  8:39 [PATCH] kernel-module-split: rrecommend kernel-image instead of rdepend Martin Hundebøll
2017-08-21  9:04 ` ✗ patchtest: failure for " Patchwork
2017-08-21  9:21 ` [PATCH v2] " Martin Hundebøll
2017-09-08 20:06   ` Paul Barker
2017-09-08 20:20     ` Andre McCurdy
2017-09-08 20:37     ` Denys Dmytriyenko
     [not found]       ` <75F5325D-9BEC-49A6-AEF8-75448B46BCF7@prevas.dk>
2017-09-08 21:29         ` Paul Barker
2017-09-11  7:02           ` Martin Hundebøll
2017-09-11  9:26             ` Richard Purdie
2017-09-11 12:19               ` Martin Hundebøll
2017-09-11 12:50                 ` 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=1505134251.18640.2.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mnhu@prevas.dk \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pbarker@toganlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox