On Sun, Jan 9, 2011 at 11:12, Kfir Lavi <[email protected]> wrote: > > > On Sun, Jan 9, 2011 at 6:05 PM, Kfir Lavi <[email protected]> wrote: > >> >> >> On Sun, Jan 9, 2011 at 5:04 PM, Zac Medico <[email protected]> wrote: >> >>> On 01/09/2011 04:00 AM, Kfir Lavi wrote: >>> > Hi, >>> > I have created an ebuild that build for me a small system. >>> > The RDEPEND has required packages. This works fine and when I emerge >>> this >>> > ebuild, >>> > all the "dependencies" are installed. >>> > When I add >>> > sys-kernel/gentoo-sources >>> > or >>> > =sys-kernel/vanilla-sources-2.6.28 >>> > Emerge just ignore this dependency and install all the other packages. >>> > Is there any mechanism that portage ignore kernel sources as a >>> dependency? >>> >>> My first guess it that you have packages that satisfy those dependencies >>> inside /etc/portage/profile/package.provided. >>> >>> If that's not the case, then I'd suggest to file a bug at >>> bugs.gentoo.org and post emerge --pretend --debug output for the command >>> that is not pulling in the expected dependencies. >>> -- >>> Thanks, >>> Zac >>> >>> It seems like problem like you stated. >> It did grab the kernel, in a middle of new install. >> I still haven't traced why this happening. >> >> Is there a flag that I can emerge with, to see the decisions of portage? >> >> Regards, >> Kfir >> > > Ok, > Deleting the target directory, and running again the ebuild, resulted linux > was grabbed by the ebuild. > I don't know why it was like that before. > > Regards, > Kfir >
If you're using the ebuild command you need to have it clean the directory after you have changed the ebuild (ie, ebuild foobar.ebuild clean). Otherwise, the system will use the cached ebuild and environment. Best, Ross
