From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] core-image-gtk-directfb, qt4e-demo-image: Remove module-init-tools from IMAGE_INSTALL list
Date: Fri, 15 Jun 2012 14:36:16 +0100 [thread overview]
Message-ID: <2973338.6EnvHsnj7v@helios> (raw)
In-Reply-To: <4FDB32BA.9060004@intel.com>
On Friday 15 June 2012 16:03:54 Laurentiu Palcu wrote:
> On 06/14/2012 08:05 PM, Saul Wold wrote:
> >> As module-init-tools package does not exist anymore there's no reason to
> >> > have it in the IMAGE_INSTALL package list. If RPM package manager is
> >> > used, build will fail with:
> >> >
> >> > Unable to find package module-init-tools (module-init-tools)!
> >
> > Do we need to replace it with kmod?
> >
> > Sau!
>
> kmod gets installed in the final image without adding it into the
> IMAGE_INSTALL list. I couldn't, yet, figure out how... :( It's not in
> the IMAGE_INSTALL and it's not in the RDEPENDS of any other package.
> Maybe I missed something. If someone can put some light on this, I would
> appreciate it.
It's because of the following dependency chain:
task-core-basic -> task-core-basic-extended -> module-init-tools
Since the kmod package RPROVIDES module-init-tools it gets installed.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-06-15 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 13:01 [PATCH] core-image-gtk-directfb, qt4e-demo-image: Remove module-init-tools from IMAGE_INSTALL list Laurentiu Palcu
2012-06-14 17:05 ` Saul Wold
2012-06-15 13:03 ` Laurentiu Palcu
2012-06-15 13:36 ` Paul Eggleton [this message]
2012-06-18 16:48 ` Saul Wold
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=2973338.6EnvHsnj7v@helios \
--to=paul.eggleton@linux.intel.com \
--cc=laurentiu.palcu@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.