On Mon, 2010-05-17 at 16:21 +0200, Vegard Nossum wrote:On 17 May 2010 15:21, James Bottomley
Even if the problem is different from zypper's, it is also here
possible to get an unsatisfiable instance. You are right that, yes,
the kconfig files on their own should always be satisfiable. But
that's before the user has made any choices at all. An example of an
unsatisfiable instance would be one where the user demands that 1.
some USB driver is enabled, while 2. USB support in general is
disabled.
Actually, these are two separate problems. The first is basic
consistency within the Kconfig subsytstem (something that select
currently damages for us). The second is what to present to the user,
which is where the inception of the select problem came from. A user
doesn't really want to know that USB device X depends on usb storage,
SCSI and a raft of other things ... they just want it to configure a
kernel that supports their device. In particular, we don't want to
present every possible option to users and then try to work out a
solution, we really need guided configuration (which, in some measure,
is what we have today: if you don't select general USB, you won't see
any USB drivers. Or more importantly, if you select an Adaptec SCSI
card, we just enable whichever transport library it needs).