From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17054 invoked by uid 1002); 22 Oct 2003 18:27:03 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 9526 invoked from network); 22 Oct 2003 18:27:02 -0000 From: "C. Brewer" To: gentoo-dev@gentoo.org Date: Wed, 22 Oct 2003 11:27:07 -0700 User-Agent: KMail/1.5.4 References: <4866.146.176.63.67.1066740482.squirrel@mail.codewordt.co.uk> <200310212044.30947.cbrewer@stealthaccess.net> <200310221017.43833.pauldv@gentoo.org> In-Reply-To: <200310221017.43833.pauldv@gentoo.org> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_8vsl/6lr9TlEvEV"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200310221127.08345.cbrewer@stealthaccess.net> Subject: Re: [gentoo-dev] USE Linux 2.6.x X-Archives-Salt: 850fd179-afe5-4fc5-87d3-4a432f944119 X-Archives-Hash: 1007edba2ed3422983e83d9363d0f655 --Boundary-02=_8vsl/6lr9TlEvEV Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline 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. =46orgive me then. I must've just assumed that when Linus said "you should'= nt do=20 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=20 believe you meant to say the kernel sources ebuild provides that link, whic= h=20 Patrick suggested that could be easily put out of date, and Spider suggeste= d=20 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 i= t=20 preexists, so the benefit is that your unattended install just dumped your= =20 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= =20 modules go, doesn't this become user preference rather than system=20 preference? There is no easy answer to this problem, but it seems nobody want to tackle= it=20 either( along with multiple versions of the same modules packages.) =2D-=20 Chuck Brewer Registered Linux User #284015 Get my gpg public key at pgp.mit.edu!! Encrypted e-mail preferred. --Boundary-02=_8vsl/6lr9TlEvEV Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQA/lsv8GmszwkJY878RAmgmAJ9q74hseZx1327jpUTO/Th8XBTT+gCfaEni FjUy7vagQgUg9iJWDkuTImc= =QwiU -----END PGP SIGNATURE----- --Boundary-02=_8vsl/6lr9TlEvEV--