TurkShell v1.0

Owner : www-data

PHP Version

5.6.40-0+deb8u12

Disk Space

40.98 GB

Server Addr

19-www4

Your IP

10.10.10.40

Edit File

File:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Configuring the interactive dependency resolver</title><link rel="stylesheet" type="text/css" href="aptitude.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="aptitude user's manual"><link rel="up" href="ch02s03.html" title="Resolving package dependencies"><link rel="prev" href="ch02s03s04.html" title="Costs in the interactive dependency resolver"><link rel="next" href="ch02s04.html" title="Search patterns"><link rel="preface" href="pr01.html" title="Introduction"><link rel="chapter" href="ch01.html" title="Chapter 1. Getting started"><link rel="chapter" href="ch02.html" title="Chapter 2. aptitude reference guide"><link rel="chapter" href="ch03.html" title="Chapter 3. aptitude frequently asked questions"><link rel="chapter" href="ch04.html" title="Chapter 4. Credits"><link rel="reference" href="rn01.html" title="Command-line reference"><link rel="refentry" href="rn01re01.html" title="aptitude"><link rel="refentry" href="rn01re02.html" title="aptitude-create-state-bundle"><link rel="refentry" href="rn01re03.html" title="aptitude-run-state-bundle"><link rel="subsection" href="ch02s03s05.html#secDependencyResolutionHints" title="Configuring resolver hints"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Configuring the interactive dependency resolver</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s03s04.html"><img src="images/prev.gif" alt="Prev"></a> </td><th width="60%" align="center">Resolving package dependencies</th><td width="20%" align="right"> <a accesskey="n" href="ch02s04.html"><img src="images/next.gif" alt="Next"></a></td></tr></table><hr></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="secDependencyResolutionConfiguration"></a>Configuring the interactive dependency resolver</h3></div></div></div><div class="toc"><dl class="toc"><dt><a href="ch02s03s05.html#secDependencyResolutionHints">Configuring resolver hints</a></dt></dl></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="secDependencyResolutionHints"></a>Configuring resolver hints</h4></div></div></div>
	 To improve the quality of the dependency solutions that
	 you receive, you can provide hints to the interactive
	 dependency resolver. These hints can alter the priorities
	 of the resolver, biasing it more strongly in favor of one
	 version or package, or they can be used to
	 “pre-load” the resolver with rejections and
	 approvals, as if you had entered the resolver and manually
	 rejected or approved various versions.
	 
	 Hints are stored in the <code class="systemitem">apt</code> configuration file,
	 <code class="filename">/etc/apt/apt.conf</code>, in the
	 configuration group “<code class="literal"><a class="link" href="ch02s05s05.html#configProblemResolver-Hints">Aptitude::ProblemResolver::Hints</a></code>”
	 (see <a class="xref" href="ch02s05s05.html" title="Configuration file reference">the section called “Configuration file reference”</a> for details on the
	 configuration file).
	 
	 Each resolver hint consists of an
	 <code>action</code>, a
	 <code>target</code>, and an optional
	 <code>version</code>. A hint is written
	 like this: <code class="literal">"<code>action</code>
	 <code>target</code>
	 [<code>version</code>]"</code>.
	 To apply a resolver hint, aptitude locates one or more
	 packages using the value of
	 <code>target</code>, chooses one or more
	 versions of those packages using the value of
	 <code>version</code>, and finally performs
	 the given <code>action</code>.
	 
	 The <code>action</code> field of a resolver
	 hint may be one of the following:
	 <div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
		“<code class="literal">approve</code>”: Approve the
		version, as if the command <a class="link" href="ch02s01s02.html#menuResolverApprove">Resolver → Toggle Approved (a)</a>
		had been invoked on it.
	 </li><li class="listitem">
		“<code class="literal">reject</code>”: Reject the
		version, as if the command <a class="link" href="ch02s01s02.html#menuResolverReject">Resolver → Toggle Rejected (r)</a>
		had been invoked on it.
	 </li><li class="listitem"><a name="hintDiscard"></a>
 “<code class="literal">discard</code>”: Discard
 every solution containing the version. Differs from
 “<code class="literal">reject</code>” in that it is
 not visible to the user and cannot be modified
 interactively.
 </li><li class="listitem">
		“<code class="literal">increase-safety-cost-to
		<code>number</code></code>”:
		increase the safety cost of any solution that contains
		the version to <code>number</code>; if
		its safety cost is already higher than
		<code>number</code>, this hint has no
		effect. The safety cost can be used (and is used by
		default) to control the order in which solutions
		appear; see <a class="xref" href="ch02s03s04.html#secDependencyResolutionCostsAndCostComponents" title="Costs and cost components">the section called “Costs and cost components”</a>
		and <a class="xref" href="ch02s03s04.html#secDependencyResolutionCostsSafetyCosts" title="Safety costs">the section called “Safety costs”</a>
		for details.
	 
		Several special cost levels can be chosen by name:

<div class="orderedlist"><ol class="orderedlist" type="a"><li class="listitem">
 <code class="literal">conflict</code>,
 <code class="literal">discard</code>: instead of changing
 the safety cost, discard solutions containing
 the version as if the “<a class="link" href="ch02s03s05.html#hintDiscard"><code class="literal">discard</code></a>”
 hint had been applied.
 </li><li class="listitem">
		 <code class="literal">maximum</code>: the highest safety
		 cost.
		 </li><li class="listitem">
		 <code class="literal">minimum</code>: the lowest safety
		 cost. All searches start at this cost, so
		 “increasing” a version to this cost
		 has no effect. However, this value can also be
		 used when adjusting the predefined cost levels:
		 for instance, setting <a class="link" href="ch02s05s05.html#configProblemResolver-Remove-Level"><code class="literal">Aptitude::ProblemResolver::Remove-Level</code></a>
		 to “<code class="literal">minimum</code>”
		 will cause removed packages to have no effect on
		 the safety cost of a solution.
		 </li></ol></div>
	 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="images/note.png"></td><th align="left">Note</th></tr><tr><td align="left" valign="top">
		 The <code class="literal">increase-safety-cost-to</code> hint
		 is applied in addition to any
		 default safety cost that is due to the selected
		 action. For instance, a hint that increases the
		 safety cost of “install
		 <code class="systemitem">hal</code> from
		 <code class="systemitem">experimental</code>” to
		 15,000 will have no effect, because that action
		 already has a safety cost of 50,000 (assuming that
		 this version of <code class="systemitem">hal</code> is not
		 the default candidate version).
		</td></tr></table></div></li><li class="listitem">
		“<code>number</code>”: add
		the given <code>number</code> to the
		version's <code>score</code>, biasing
		the resolver in favor of it or (with a negative
		number) away from it. For instance, the hint
		<code class="literal">200 emacs</code> adds 200 to the score of
		<code class="literal">emacs</code>, whereas the hint
		<code class="literal">-10 emacs</code> subtracts 10 from its
		score.
	 </li></ol></div>
	 If <code>target</code> field of a resolver
	 hint contains a question mark
	 (“<code class="literal">?</code>”) or tilde
	 (“<code class="literal">~</code>”), it is considered to
	 be a search pattern and all matching package versions are
	 considered. Otherwise, it is considered to be the name of
	 a package to select. So the target
	 “<code class="literal">g++</code>” will select only the
	 <code class="literal">g++</code> package, but the target
	 “<code class="literal">?section(non-free)</code>” will
	 select any package in the <code class="literal">non-free</code>
	 section. See <a class="xref" href="ch02s04.html" title="Search patterns">the section called “Search patterns”</a> for more
	 information on search patterns.
	 
	 If the <code>version</code> field is not
	 present, then all versions of the package are affected by
	 the hint. Otherwise, it may have any of the following
	 forms:
	 <div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
		“<code class="literal">/<code>archive</code></code>”:
		the hint only affects versions that are available in
		the given <code>archive</code>.
	 </li><li class="listitem">
		“<code class="literal">&lt;<code>version</code></code>”:
		the hint only affects versions whose version number is
		less than <code>version</code>.
	 </li><li class="listitem">
		“<code class="literal">&lt;=<code>version</code></code>”:
		the hint only affects versions whose version number is
		less than or equal to
		<code>version</code>.
	 </li><li class="listitem">
		“<code class="literal">=<code>version</code></code>”:
		the hint only affects versions whose version number is
		<code>version</code>.
	 </li><li class="listitem">
		“<code class="literal">&lt;&gt;<code>version</code></code>”:
		the hint only affects versions whose version number is
		not <code>version</code>.
	 </li><li class="listitem">
		“<code class="literal">&gt;=<code>version</code></code>”:
		the hint only affects versions whose version number is
		greater than or equal to
		<code>version</code>.
	 </li><li class="listitem">
		“<code class="literal">&gt;<code>version</code></code>”:
		the hint only affects versions whose version number is
		greater than <code>version</code>.
	 </li><li class="listitem">
		“<code class="literal">:UNINST</code>”: instead of
		affecting any of the versions of
		<code>target</code>, the hint affects
		the decision to remove
		<code>target</code>. For instance,
		“<code class="literal">reject aptitude
		:UNINST</code>” will prevent the resolver
		from attempting to remove aptitude.
	 </li><li class="listitem">
		“<code>version</code>”: the
		hint only affects versions whose version number is
		<code>version</code>.
	 </li></ol></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02s03s04.html"><img src="images/prev.gif" alt="Prev"></a> </td><td width="20%" align="center"><a accesskey="u" href="ch02s03.html"><img src="images/up.gif" alt="Up"></a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s04.html"><img src="images/next.gif" alt="Next"></a></td></tr><tr><td width="40%" align="left" valign="top">Costs in the interactive dependency resolver </td><td width="20%" align="center"><a accesskey="h" href="index.html"><img src="images/home.gif" alt="Home"></a></td><td width="40%" align="right" valign="top"> Search patterns</td></tr></table></div></body></html>