public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org,
	kbuild-devel@lists.sourceforge.net
Subject: [RFC] select and dependencies in Kconfig
Date: Wed, 16 May 2007 04:33:35 +0100	[thread overview]
Message-ID: <20070516033335.GH4095@ftp.linux.org.uk> (raw)
In-Reply-To: <E1Ho2om-0003TN-Ah@ZenIV.linux.org.uk>

On Tue, May 15, 2007 at 08:36:20PM +0100, Al Viro wrote:
> 
> stuff that does select USB should depend on USB_ARCH_HAS_HCD, or we'll
> end up with unbuildable configs.

BTW, this kind of situation happens often enough, so how about doing
the following: teach kconfig that if FOO selects BAR and BAR depends
on <expr>, we should act as if FOO had explicit depends on <expr>.

Rationale: if FOO selects BAR, BAR depends on <expr> and <expr> is false,
turning FOO on will land us into unbuildable configuration (BAR turned on,
dependencies of BAR are not satisfied).  It really happens often enough to
be very annoying.  And we have fsckloads of dependencies that are there
only because of such scenarios.  Gets especially nasty when BAR is selected
by several dozens of options and dependencies of BAR change...

Implementing that is pretty simply; the only thing I'm not sure how to deal
with is how to show such inherited dependencies in menuconfig et.al.

Comments?

  reply	other threads:[~2007-05-16  3:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 19:36 [PATCH] missing dependencies for USB drivers in input Al Viro
2007-05-16  3:33 ` Al Viro [this message]
2007-05-16  3:48   ` [RFC] select and dependencies in Kconfig Linus Torvalds
2007-05-16 14:20     ` Satyam Sharma
2007-05-16 15:31       ` Satyam Sharma
2007-05-16  8:38   ` Russell King
2007-05-16 14:24   ` Stefan Richter
2007-05-16 23:30     ` Timur Tabi
2007-05-17  0:16       ` Stefan Richter
2007-05-17  0:32       ` Stefan Richter
2007-05-18  3:38   ` Roman Zippel

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=20070516033335.GH4095@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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