1 |
Thanks a lot for the answers. |
2 |
(I answer between your lines) |
3 |
|
4 |
On Wed, Dec 01, 2004 at 06:21:20PM -0700, Duncan wrote: |
5 |
> |
6 |
> OK, I know nothing about catalyst, and am just a user generally lurking on |
7 |
> the dev list, but... this one's a portage question at least in part, and I |
8 |
> /think/ I can answer that side of it. |
9 |
> |
10 |
> Virtuals, in portage, mean any single package of a group of packages (all |
11 |
> with provides=<the virtual in question>) may meet the requirements. If |
12 |
> one is already installed, great, that satisfies the requirement. If no |
13 |
> such literal package fulfilling the requirement is yet installed, however, |
14 |
> portage falls back to a default choice. |
15 |
The default choice is specified in the virtuals, isn't it? |
16 |
|
17 |
> |
18 |
> What you have here is portage falling back to a 2.4 default choice, a 2.4 |
19 |
> kernel and kernel-headers, while you want 2.6 versions. For a live |
20 |
> install, you'd simply install your chosen 2.6 version which would then |
21 |
> provide the virtual you needed. |
22 |
> |
23 |
> I'm on amd64 and as I said haven't worked with catalyst, but AFAIK, what |
24 |
> you need to do there is fix the profile such that the defaults are 2.6. |
25 |
> Why are you still using a 2004.2 profile for one thing? The 2004.3 |
26 |
> profile, if I'm not mistaken, defaults to kernel 2.6 along with updating |
27 |
> other requirements appropriately. If you have no specific reason not to, |
28 |
> I'd suggest updating to the 2004.3 profile. |
29 |
Ok, I'll just try the 2004.3 profile. I thought 2004.2 had 2.6 virtuals. |
30 |
--- |
31 |
I just tried the profile. There isn't a virtuals definition in it! |
32 |
(Portage 20041108) |
33 |
|
34 |
> |
35 |
> If there's a specific reason not to do 2004.3, keep in mind that the |
36 |
> profile you are using is a cascading profile (which means you should be |
37 |
> using portage 2.0.51 as .50 had issues with cascading profiles). Thus, |
38 |
> the defaults from further up the tree are used if a profile itself doesn't |
39 |
> over-rule them. Dirs further /down/ the tree are NOT used, but are there |
40 |
> for those who want them as a special case, therefore, the gcc34 subdir of |
41 |
> your profile is a special case of the 2004.2 profile, with 2.6 being a |
42 |
> special case of the gcc34 special case of the 2004.2 case of the x86 case |
43 |
> of the default-linux profile. If you wish to use that 2004.2/gcc34/2.6 |
44 |
> special case, you may do so, and it should change your requirements |
45 |
> accordingly. |
46 |
|
47 |
I'm using portage 2.0.51-r4. I didn't know how cascade profiles work... I |
48 |
imagined that they worked that way similar... |
49 |
|
50 |
> |
51 |
> If that still doesn't fit your rather customized case, then simply |
52 |
> customize the requirements. Again, using cascading profiles, virtuals |
53 |
> from up the tree are used if nothing in the current profile dir overrides |
54 |
> them. Thus, the virtuals file in x86 says use gentoo-sources (a 2.4 |
55 |
> kernel) as the default virtual/linux-sources, while it falls back up to |
56 |
> default-linux to get the default for virtual/os-headers, |
57 |
> sys-kernel/linux-headers (kernel 2.4 headers). |
58 |
|
59 |
Are you talking about using the profile "portage/profiles/default-linux" instead |
60 |
of "portage/profiles/default-linux/x86/2004.2" ? |
61 |
In which case is "portage/profiles/default-linux/virtuals" read? Will that file |
62 |
be read, if I have the profile 2004.3 or 2004.2? And what about the |
63 |
portage/profiles/default-linux/x86/virtuals? |
64 |
|
65 |
> |
66 |
> Forcing 2.6 kernel and headers means placing a virtuals file in the |
67 |
> current profile, overriding those up the tree from it, with the defaults |
68 |
> you want, probably the same ones as in x86/2004.3, or in |
69 |
> x86/2004.2/gcc34/2.6, for those items. |
70 |
Hummm I think _now_ I understand the problem. I read the virtuals file in |
71 |
x86/2004.2/gcc34/2.6, and there was 2.6 virtuals. So, I thought that the |
72 |
x86/2004.2 profile had 2.6 virtuals. I thought that the cascade was going down |
73 |
to directories, and not up! I thought that that was strange... :) |
74 |
|
75 |
> |
76 |
> Because I've never used catalyst, I'm not sure where you put edits to its |
77 |
> profile. I assume you put them in the stage1root you mentioned, but |
78 |
> that's just a guess. Read the documentation, or do a bit of experimenting. |
79 |
|
80 |
Aha. I was in confusion with the 'direction' of the cascade, so I thought 2004.2 |
81 |
had virtuals. |
82 |
|
83 |
What I've tried, while answering this email: |
84 |
I've tried using 2004.3 => Still keeps on using 2.4 (there are no virtual |
85 |
definitions in 2004.3!) |
86 |
I've tried using default-linux/x86/2004.2/gcc34/2.6/ as profile => Even this way |
87 |
emerge still keeps on using 2.4 |
88 |
I've tried changing the content of the virtuals in default-linux and |
89 |
default-linux/x86 => YES! Now it installs 2.6 headers. |
90 |
|
91 |
But... Shouldn't the other tries work ??? At least, you say that about 2004.3, |
92 |
and the profile ....gcc34/2.6/ seems to have virtuals defined there. |
93 |
|
94 |
Thanks! |
95 |
|
96 |
-- |
97 |
gentoo-dev@g.o mailing list |