[gentoo-dev] Re: About linux-headers, making stages with catalyst

[Duncan]

Lluís Batlle i Rossell posted
<20041201222109.GA20954@××××××××××××××××××.net>, excerpted below,  on Wed,
01 Dec 2004 23:21:09 +0100:

> That "emerge" call, as a dependence, tries to install "linux-headers".
> In a similar case, using the same profile, it happens that "emerge"
> tries to install "gentoo-sources-2.4..." when emerging "device-mapper"
> (which depends on virtual/linux-source).
>
> Where does "emerge" read that it has to install "2.4" things? There are
> only the "virtuals" in the profile, isn't it? And they relate to 2.6...
> I really don't know how to tell emerge not to use "2.4" things, as I
> know only that he reads the "virtuals" for satisfying virtuals'
> dependencies.

OK, I know nothing about catalyst, and am just a user generally lurking on
the dev list, but... this one's a portage question at least in part, and I
/think/ I can answer that side of it.

Virtuals, in portage, mean any single package of a group of packages (all
with provides=<the virtual in question>) may meet the requirements.  If
one is already installed, great, that satisfies the requirement.  If no
such literal package fulfilling the requirement is yet installed, however,
portage falls back to a default choice.

What you have here is portage falling back to a 2.4 default choice, a 2.4
kernel and kernel-headers, while you want 2.6 versions.  For a live
install, you'd simply install your chosen 2.6 version which would then
provide the virtual you needed.

I'm on amd64 and as I said haven't worked with catalyst, but AFAIK, what
you need to do there is fix the profile such that the defaults are 2.6.
Why are you still using a 2004.2 profile for one thing?  The 2004.3
profile, if I'm not mistaken, defaults to kernel 2.6 along with updating
other requirements appropriately.  If you have no specific reason not to,
I'd suggest updating to the 2004.3 profile.

If there's a specific reason not to do 2004.3, keep in mind that the
profile you are using is a cascading profile (which means you should be
using portage 2.0.51 as .50 had issues with cascading profiles).  Thus,
the defaults from further up the tree are used if a profile itself doesn't
over-rule them.  Dirs further /down/ the tree are NOT used, but are there
for those who want them as a special case, therefore, the gcc34 subdir of
your profile is a special case of the 2004.2 profile, with 2.6 being a
special case of the gcc34 special case of the 2004.2 case of the x86 case
of the default-linux profile.  If you wish to use that 2004.2/gcc34/2.6
special case, you may do so, and it should change your requirements
accordingly.

If that still doesn't fit your rather customized case, then simply
customize the requirements.  Again, using cascading profiles, virtuals
from up the tree are used if nothing in the current profile dir overrides
them.  Thus, the virtuals file in x86 says use gentoo-sources (a 2.4
kernel) as the default virtual/linux-sources, while it falls back up to
default-linux to get the default for virtual/os-headers,
sys-kernel/linux-headers (kernel 2.4 headers).

Forcing 2.6 kernel and headers means placing a virtuals file in the
current profile, overriding those up the tree from it, with the defaults
you want, probably the same ones as in x86/2004.3, or in
x86/2004.2/gcc34/2.6, for those items.

Because I've never used catalyst, I'm not sure where you put edits to its
profile.  I assume you put them in the stage1root you mentioned, but
that's just a guess.  Read the documentation, or do a bit of experimenting.

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin



--
gentoo-dev@g.o mailing list