From: Andi Kleen <andi@firstfloor.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Bart Massey <bart@cs.pdx.edu>, Michal Marek <mmarek@suse.cz>,
Greg Kroah-Hartman <greg@kroah.com>, Ingo Molnar <mingo@elte.hu>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: [ANNOUNCE] GSoC project: Improving kconfig using a SAT solver
Date: Mon, 17 May 2010 16:18:57 +0200 [thread overview]
Message-ID: <20100517141857.GA5947@basil.fritz.box> (raw)
In-Reply-To: <AANLkTiktV26Xu_qXFPdTRMLe5UwWnjpqvEKitjRElF6R@mail.gmail.com>
> You bring up a valid point, and I admittedly haven't given it VERY
> much thought yet, but I think that conflicts could be displayed in the
> following way: If an instance is unsolvable, then it means that all
> possible valuations/assignments make at least one clause (disjunction)
> false. Each clause is usually generated by exactly one dependency
> specification (the "depends on" directive), so we could print these
> dependencies to the screen as suggestions for how to resolve the
> conflict.
The problem is that might be a lot of entries, e.g. for "depends on PCI"
You then end up displaying pages and pages of information, which
is very hard to make sense of.
You can see that by playing around with libzypp dependencies.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-05-17 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 12:02 [ANNOUNCE] GSoC project: Improving kconfig using a SAT solver Vegard Nossum
2010-05-17 12:13 ` Andi Kleen
2010-05-17 13:09 ` Vegard Nossum
2010-05-17 13:21 ` James Bottomley
2010-05-17 14:21 ` Vegard Nossum
2010-05-17 14:28 ` James Bottomley
2010-05-18 6:03 ` david
2010-05-18 12:26 ` Jon Smirl
2010-05-18 12:54 ` Vegard Nossum
2010-05-18 13:42 ` kevin granade
2010-06-10 13:55 ` Pavel Machek
2010-05-17 14:18 ` Andi Kleen [this message]
2010-05-19 11:05 ` Felipe Contreras
2010-05-19 18:31 ` Vegard Nossum
2010-05-21 11:07 ` Felipe Contreras
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=20100517141857.GA5947@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bart@cs.pdx.edu \
--cc=greg@kroah.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mmarek@suse.cz \
--cc=vegard.nossum@gmail.com \
/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