From: Andi Kleen <andi@firstfloor.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: 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 14:13:58 +0200 [thread overview]
Message-ID: <87tyq63eux.fsf@basil.nowhere.org> (raw)
In-Reply-To: <AANLkTil73ArhX2w6b_v1bmWjP1FA5zUTfPzK2N4waOu1@mail.gmail.com> (Vegard Nossum's message of "Mon\, 17 May 2010 14\:02\:15 +0200")
Vegard Nossum <vegard.nossum@gmail.com> writes:
> I just wanted to say that I've been accepted into this year's Google
> Summer of Code program and will spend this summer working on improving
> the kconfig system in a very particular direction: I want to integrate
> a proper boolean constraint satisfiability solver into the
> configuration editors (menuconfig, etc.) in order to allow
> partial/incomplete configuration specifications. In short, this means
> that the user can choose to not specify a particular value for some
> config options, but let the system deduce their values. This will
> hopefully improve usability and also solve the select problem once and
> for all.
Nice idea. I read your proposal and it looks good.
I assume you got inspired by the libzypp use of a SAT solver
for package dependencies? One problem that is visible there
is that it can be hard to display conflicts in a nice and understandable
way to the user, especially if there are lots of dependencies.
It might be worth planning in some time to solve that nicely.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-05-17 12:14 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 [this message]
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
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=87tyq63eux.fsf@basil.nowhere.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.