[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070507135052.cc7e74ca.randy.dunlap@oracle.com>
Date: Mon, 7 May 2007 13:50:52 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Jeff Garzik <jeff@...zik.org>
Cc: Satyam Sharma <satyam.sharma@...il.com>,
Roman Zippel <zippel@...ux-m68k.org>,
Krzysztof Halasa <khc@...waw.pl>,
Russell King <rmk@....linux.org.uk>,
lkml <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org,
linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [PATCH 1/3] WAN Kconfig: change "depends on HDLC" to "select"
On Mon, 07 May 2007 16:31:48 -0400 Jeff Garzik wrote:
> Satyam Sharma wrote:
> > Yes, mixing select and depends is a recipe for build disasters. Call
> > me a rabid fanatic, but I would in fact go as far as to say that this
> > whole "select" thing in the Kconfig process is one big BUG, and not a
> > feature. People are lazy by nature and would rather just "select" a
> > dependency for their config option than burden users with several
> > "depends".
>
> Tough, the kernel community has voted against you.
Andrew (usually) implores people not to use "select" and I agree
with him.
> It makes far more sense to include a driver during kernel configuration,
> and have that driver pull in its libraries via 'select'. The lame
> alternative requires developers to know which libraries they need BEFORE
> picking their drivers, which is backwards and requires legwork on the
> part of the kernel developer.
Developers? If you had said "users," I might agree, but IMO it's
OK (or even Good) for developers to know what libraries their code
uses/requires. Yes, that's a good thing.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists