From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga11.intel.com ([192.55.52.93]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SfWrc-00053w-ST for openembedded-core@lists.openembedded.org; Fri, 15 Jun 2012 15:47:01 +0200 Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 15 Jun 2012 06:36:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="180548854" Received: from unknown (HELO helios.localnet) ([10.252.120.157]) by fmsmga002.fm.intel.com with ESMTP; 15 Jun 2012 06:36:20 -0700 From: Paul Eggleton To: Laurentiu Palcu Date: Fri, 15 Jun 2012 14:36:16 +0100 Message-ID: <2973338.6EnvHsnj7v@helios> Organization: Intel Corporation User-Agent: KMail/4.8.3 (Linux/3.2.0-25-generic-pae; KDE/4.8.3; i686; ; ) In-Reply-To: <4FDB32BA.9060004@intel.com> References: <1339678865-3610-1-git-send-email-laurentiu.palcu@intel.com> <4FDA19CD.3080003@linux.intel.com> <4FDB32BA.9060004@intel.com> MIME-Version: 1.0 Cc: openembedded-core@lists.openembedded.org Subject: Re: [PATCH] core-image-gtk-directfb, qt4e-demo-image: Remove module-init-tools from IMAGE_INSTALL list X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 13:47:01 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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