public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE Linux 2.6.x
Date: Wed, 22 Oct 2003 10:17:27 +0200	[thread overview]
Message-ID: <200310221017.43833.pauldv@gentoo.org> (raw)
In-Reply-To: <200310212044.30947.cbrewer@stealthaccess.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 22 October 2003 05:44, C. Brewer wrote:
<cut>

> Okay, this part comes across barely intelligible, but if it helps
> substitute TARGET= for SLOT=.. of course I did point out it was a
> suggestion, not a solution, and you have offered up what counterproposal?

<cut>

> "I" don't want to have it depend on a running kernel, or on a symlink, All
> I was saying is that in most cases it'd probably be just easier to boot
> into a running kernel and build your non-essential mod package, I realize
> that this is not always the case.
>
> > Yes, this thread invoked a lot of hot emotions from my side.
> >
> >
> > // Spider
>
> Well, guess what? I was pretty pissed off _before_  I saw your mail, so you
> can imagine where I'm at now, especially since I've asked a couple of times
> why this symlink is necessary, when it's highly discouraged. If a package
> needs this symlink, mask it, get it fixed upstream or dont carry it at all
> ffs. I point out the bad ones when I see them, and I atleast proffered a
> suggestion. I was civil when this was a discussion, but turning this into a
> pissing match was sheer stupidity. But I guess I'm just the stupid end user
> with no say, I guess? Atleast when I'm being a prick, I only represent me.

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.

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.

Paul

- -- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/lj0nbKx5DBjWFdsRAtzFAKDkYB87M/SEpLNFl3jriMWlVdmwZgCfabqw
UKDJcY/TghcKTP7NVL24JX0=
=B3yP
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-10-22  8:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 12:48 [gentoo-dev] USE Linux 2.6.x Dhruba Bandopadhyay
2003-10-21 12:58 ` Mike Frysinger
2003-10-21 15:39   ` C. Brewer
2003-10-21 16:25     ` Thomas de Grenier de Latour
2003-10-21 17:44       ` C. Brewer
2003-10-21 20:15         ` Grant Goodyear
2003-10-22  3:11           ` C. Brewer
2003-10-21 20:53         ` Martin Schlemmer
2003-10-21 22:25         ` Spider
2003-10-22  3:44           ` C. Brewer
2003-10-22  8:15             ` Chris Smith
2003-10-22  8:17             ` Paul de Vrieze [this message]
2003-10-22 18:27               ` C. Brewer
2003-10-22 18:46                 ` Brian Jackson
2003-10-22 19:23                 ` Paul de Vrieze
2003-10-22 19:47                   ` C. Brewer
2003-10-22 20:06                     ` Spider
2003-10-22 10:40             ` Spider
2003-10-22 18:07               ` C. Brewer
2003-10-22 19:01                 ` Spider
2003-10-22 11:20           ` Patrick Lauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200310221017.43833.pauldv@gentoo.org \
    --to=pauldv@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox