From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752707Ab0EQOTG (ORCPT ); Mon, 17 May 2010 10:19:06 -0400 Received: from one.firstfloor.org ([213.235.205.2]:47562 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751878Ab0EQOTD (ORCPT ); Mon, 17 May 2010 10:19:03 -0400 Date: Mon, 17 May 2010 16:18:57 +0200 From: Andi Kleen To: Vegard Nossum Cc: Andi Kleen , linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, Bart Massey , Michal Marek , Greg Kroah-Hartman , Ingo Molnar , James Bottomley Subject: Re: [ANNOUNCE] GSoC project: Improving kconfig using a SAT solver Message-ID: <20100517141857.GA5947@basil.fritz.box> References: <87tyq63eux.fsf@basil.nowhere.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > 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.