Re: [gentoo-dev] USE Linux 2.6.x

["C. Brewer" <cbrewer@stealthaccess.net>]

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2185 bytes --]

On Wednesday 22 October 2003 1:17, Paul de Vrieze wrote:


> This symlink is not highly discouraged. It is highly discouraged to use a
> plain kernel tree as source for the /usr/include/linux headers. Those
> symlinks mean problems. It is also discouraged to assume that
> /usr/src/linux points to the RUNNING kernel, those sources can be found by
> /lib/modules/ `uname -r`/build. However in this case we want a way against
> which kernel modules should be build.

Forgive me then. I must've just assumed that when Linus said "you should'nt do 
that" with his package, that was highly discouraged.

> I wonder why you insist on having an awkward, notworking way of doing so.
> Gentoo is about unattended installs. Such an environment variable violates
> it. Further it would break initial installs. When one does an emerge kde
> after system is just merged, it will pull in a kernel source (for alsa),
> however if you don't specify your variable building alsa-driver still
> fails. However the kernel sources automatically install the linux symlink
> if it did not exist yet (but not change it if it did). Of course we could
> use another name/location, but I don't see the point.

Well I did not say my way was a definative answer, merely a suggestion. I 
believe you meant to say the kernel sources ebuild provides that link, which 
Patrick suggested that could be easily put out of date, and Spider suggested 
he might not keep the sources for. But how is my asking the link get dropped
"awkward and notworking"? You just pointed out the link doesn't change if it 
preexists, so the benefit is that your unattended install just dumped your 
modules into the wrong place, when you have it pointing at the wrong kernel.
So if you need to keep changing this link back and forth to suit where the 
modules go, doesn't this become user preference rather than system 
preference?

There is no easy answer to this problem, but it seems nobody want to tackle it 
either( along with multiple versions of the same modules packages.)
-- 
Chuck Brewer
Registered Linux User #284015
Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred.



[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]