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.

1 files changed, 16 insertions, 0 deletions

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</screen>
 	      </seg>
 	    </seglistitem>
 
+	    <seglistitem id='configProblemResolver-FutureHorizon'>
+	      <seg><literal>Aptitude::ProblemResolver::FutureHorizon</literal></seg>
+	      <seg><literal>50</literal></seg>
+
+	      <seg>
+		How many <quote>steps</quote> 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.
+	      </seg>
+	    </seglistitem>
+
 	    <seglistitem id='configProblemResolver-Hints'>
 	      <seg><literal>Aptitude::ProblemResolver::Hints</literal></seg>
 	      <seg>(empty)</seg>