From 68c5bd8f591db4c90a3b33e9b4b230897e6b6bd5 Mon Sep 17 00:00:00 2001 From: Daniel Burrows Date: Mon, 9 Feb 2009 22:24:34 -0800 Subject: Add support to the problem resolver for searching past the first solution. (Closes: #482825) Hopefully this won't be too bad for performance, because it only searches 50 nodes past the first one. The one thing that worries me is that it does this search *every time* that the resolver runs, even if it's just going to return an enqueued solution from the last run ... but still, it should be fine unless you're generating hundreds of solutions (in which case we have an EPIC RESOLVER FAIL). I think this breaks rejects/accepts. More work needed there. --- doc/en/aptitude.xml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'doc') diff --git a/doc/en/aptitude.xml b/doc/en/aptitude.xml index 2f25da43..e327ea93 100644 --- a/doc/en/aptitude.xml +++ b/doc/en/aptitude.xml @@ -10868,6 +10868,22 @@ e: Examine !: Apply .: Next ,: Previous + + Aptitude::ProblemResolver::FutureHorizon + 50 + + + How many steps the resolver should run + after finding the first solution. Although &aptitude; + attempts to generate better solutions before worse + solutions, sometimes it is unable to do so; this + setting causes the resolver to briefly continue + searching for a better solution before displaying its + results, rather than stopping immediately after it + finds the first solution. + + + Aptitude::ProblemResolver::Hints (empty) -- cgit v1.2.3