1 |
Hi, |
2 |
|
3 |
|
4 |
I am in the process of migrating to sys-kernel/gentoo-sources (from a now |
5 |
extinct sys-kernel/gs-sources), and I was wondering about the situation |
6 |
with these two packages. |
7 |
|
8 |
The docs for module-init-tools mention that these tools are for kernels >= |
9 |
2.5.48. gentoo-sources is 2.4.26-r9 as of today. emerge -Duvp |
10 |
gentoo-sources suggests emerging module-init-tools, since its ebuild |
11 |
inherits from kernel-2.eclass, which in turn contains this: |
12 |
|
13 |
RDEPEND="${DEPEND} |
14 |
!build? ( >=sys-libs/ncurses-5.2 |
15 |
dev-lang/perl |
16 |
sys-apps/module-init-tools |
17 |
sys-devel/make )" |
18 |
|
19 |
Should this not be |
20 |
|
21 |
virtual/modutils |
22 |
|
23 |
... instead of |
24 |
|
25 |
sys-apps/module-init-tools |
26 |
|
27 |
(because it _is_ the case with kernel.eclass). My /var/cache/edb/virtuals |
28 |
contains sys-apps/modutils, and "fixing" the quirk above in |
29 |
kernel-2.eclass makes portage stop wanting to emerge module-init-tools. Is |
30 |
this a bug in kernel-2.eclass (and if so, should I file it to |
31 |
bugs.gentoo.org), or am I missing something obvious? |
32 |
|
33 |
For a second more general question -- how are these packages supposed to |
34 |
be handled? Most (relevant for me :)) profiles (x86) have |
35 |
module-init-tools "providing" virtual/modutils, which is a bit annoying |
36 |
since I have gentoo-sources. How do gentoo-sources people deal with |
37 |
modutils? |
38 |
|
39 |
TIA, |
40 |
|
41 |
|
42 |
|
43 |
|
44 |
|
45 |
ivr |
46 |
-- |
47 |
Amy: Psst... look what life was like before genetic engeneering. |
48 |
Leela: Those poor 20th century women... |
49 |
-- Futurama, "Why must I be a Crustacean in love?" |
50 |
|
51 |
-- |
52 |
gentoo-dev@g.o mailing list |