On Saturday 23 March 2013 15.06:05 Mike Gilbert wrote:
> On Sat, Mar 23, 2013 at 1:42 PM, Dan Johansson <dan.johans...@dmj.nu> wrote:
> > Hello,
> >
> > Some of my servers are running with a kernel without module-support.
> > On these servers something has started to pull in sys-apps/kmod, which when 
> > compiled complains about missing modules-support in the kernel (as it 
> > should).
> > Doing an "equery d sys-apps/kmod" I can see that the following two packages 
> > depends on sy-apps/kmod:
> > sys-fs/udev-197-r8 (kmod ? >=sys-apps/kmod-12)
> > virtual/modutils-0 (sys-apps/kmod[tools])
> >
> > sys-fs/udev has "-kmod" in its USE-flags, so that should not be an issue).
> > # emerge --verbose --pretend sys-fs/udev
> > [ebuild   R    ] sys-fs/udev-197-r8  USE="acl openrc -doc -gudev -hwdb 
> > -introspection -keymap -kmod (-selinux) -static-libs" 0 kB
> >
> > With virtual/modutils its an other thing, here we have a circular 
> > dependency between virtual/modutils and sys-apps/kmod if the tools USE-flag 
> > is set.
> 
> That circular dep is interesting; sys-apps/kmod only depends on
> virtual/modutils because it inherits linux-mod.eclass.
> 
> Could you file about about the circular dependency please?
Bug 462926 (https://bugs.gentoo.org/show_bug.cgi?id=462926) is opened for the 
circular dependency.

My more immediate  question is "Why is virtual/modutils & sys-apps/kmod pulled 
in at all?" and "How can I prevent it?"

Here the output of my "emerge update"

# emerge --update --deep --verbose --reinstall changed-use --with-bdeps y world 
--pretend --tree

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!


[nomerge       ] virtual/modutils-0 
[ebuild  N     ]  sys-apps/kmod-12-r1  USE="tools zlib -debug -doc -lzma 
-static-libs" 0 kB
[ebuild  N     ]   virtual/modutils-0  0 kB

Regards,
-- 
Dan Johansson, <http://www.dmj.nu>
***************************************************
This message is printed on 100% recycled electrons!
***************************************************

Reply via email to