From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] USE Linux 2.6.x
Date: Wed, 22 Oct 2003 12:40:20 +0200 [thread overview]
Message-ID: <20031022124020.0154ffc6.spider@gentoo.org> (raw)
In-Reply-To: <200310212044.30947.cbrewer@stealthaccess.net>
[-- Attachment #1: Type: text/plain, Size: 2719 bytes --]
begin quote
On Tue, 21 Oct 2003 20:44:23 -0700
"C. Brewer" <cbrewer@stealthaccess.net> wrote:
> On Tuesday 21 October 2003 3:25, Spider wrote:
> > begin quote
>
> > Then fix pcmcia-cs and alsa-driver before you suggest anything. as
> > it is, my machine won't boot properly without pcmcia-cs -and- alsa,
> > as they IRQ conflict unless loaded in a certain order.
> Excuse me? "I" should fix these?
Because, they are two of the problematic builds that are affected by
your suggested way of fixing, or breaking, things. This was not
personally directed at you, but taken out as examples of packages that
can't just depend on "What am I running right now" Because of how they
work.
> > And no, you won't get me to emerge it with
> > SLOT="purple-gnomes-2.4.44" either, Just because I sat down and got
> > my own kerneltree installed into
> > usr/src/testkernelwithextraJFSpatches , and then loose my existing ,
> > working, tried kernelset.
>
> 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?
Curently my counterproposal is to actually have the usr/src/linux
symlink directed at the target kernel, and if that link isn't found,
assume that we want the running kernel instead, and repoint it at
lib/modules/`uname -r`/build
Just because usr/src/linux is a symlink in our case, why is that worse
than following and relying on the /lib/modules/`uname -r`/build
symlink? The name? if that's the case, we could well make the
symlink named "Target" and instead just confuse people more.
> > When you get this set to -automagically- detect the target kernel.,
> > build modules and fix. then ok.
>
> Again with the when "i" thing...
Yes, I'm of the old school , I -assume- that people who suggest a way
of doing things, also have tried it themselves, or are capable of
implementing it. When you don't have that situation, you get "Designed
by Commite" solutions that may sound good, but are in fact unworkable.
> 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.
The personal form "i" which I used througout the whole email suggests
that in this case it is my personal opinion. To assume that it is that
of a team, whom I've been sent forth to represent, is plain silly.
And, in my not overly humble opinion, You have just as much to say as
anyone else. Its not about your email address.
//Spider
--
begin .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-10-22 10:40 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
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 [this message]
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=20031022124020.0154ffc6.spider@gentoo.org \
--to=spider@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