From: Cornelia Huck <kernel@cornelia-huck.de>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] let W1 select NET
Date: Fri, 13 Aug 2004 15:52:33 +0200 [thread overview]
Message-ID: <20040813155233.04ccac4a@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20040813105412.GW13377@fs.tum.de>
On Fri, 13 Aug 2004 12:54:12 +0200
Adrian Bunk <bunk@fs.tum.de> wrote:
> It's also relatively safe since NET itself doesn't has any
> dependencies.
Otherwise, this would be problematic. Consider the following:
config FOO
bool "foo"
select BAR
config BAR
bool
depends on BAZ
config BAZ
bool
default n
You can select FOO, which will select BAR. In your config, you'll end up with
CONFIG_FOO=y
CONFIG_BAR=y
# CONFIG_BAZ is not set
(similar result if you don't specify BAZ at all), which would get you into trouble. (I saw this while looking into what happens if s390 uses drivers/Kconfig, and got a headache why some stuff was selected by
allyesconfig that depended on pci).
Question: Is this a bug or a feature? If the latter, select should probably not be used on anything that has dependencies...
Regards,
Cornelia
next prev parent reply other threads:[~2004-08-13 13:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 10:17 Adrian Bunk
2004-08-13 10:31 ` Evgeniy Polyakov
2004-08-13 10:32 ` Roman Zippel
2004-08-13 10:46 ` Evgeniy Polyakov
2004-08-13 10:54 ` Roman Zippel
2004-08-13 11:01 ` Adrian Bunk
2004-08-13 11:26 ` Bernd Eckenfels
2004-08-13 12:11 ` Roman Zippel
2004-08-13 12:24 ` Adrian Bunk
2004-08-13 17:00 ` Randy.Dunlap
2004-08-15 17:13 ` Roman Zippel
2004-08-13 12:12 ` Russell King
2004-08-16 2:18 ` Miles Bader
2004-08-13 11:06 ` Evgeniy Polyakov
2004-08-13 10:54 ` Adrian Bunk
2004-08-13 11:06 ` Roman Zippel
2004-08-13 13:52 ` Cornelia Huck [this message]
2004-08-13 15:10 ` Evgeniy Polyakov
2004-08-13 15:45 ` Cornelia Huck
2004-08-13 17:12 ` Evgeniy Polyakov
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=20040813155233.04ccac4a@gondolin.boeblingen.de.ibm.com \
--to=kernel@cornelia-huck.de \
--cc=bunk@fs.tum.de \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®