On Wed, 2004-12-01 at 23:21 +0100, Lluís Batlle i Rossell wrote:
> I'm a user of catalyst; I'm trying to make stages for some different
> arquitectures, which use the newest portage and _at least_ linux 2.6 headers.
> I'm using the profile portage/profiles/default-linux/x86/2004.2, and there are
> virtuals which refer to linux 2.6.

I made this profile and I can assure you that 2.4 headers and a 2.4
kernel are the defaults for it and the 2004.3 profile.  There is not a
x86 profile in the portage tree that does not have 2.4 as the defaults
yet.

> When catalyst tries to build stage 1 (from a stage 3), it creates a "stage1root"
> in /tmp. There are copied the portage profile, and little more. Then, "emerge"
> is called for installing the base packages, using environment variable "ROOT".
> 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).

This is expected behavior thanks to the profile's virtuals.

> 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.

You are correct in that the virtuals file is read.  The easiest way
would be for you to create your own profile and use that instead.

> I hope I wrote my problem clear enough. I'm not too good writting in English. :)

-- 
Chris Gianelloni
Release Engineering - Operational/QA Manager
Games - Developer
Gentoo Linux