aboutsummaryrefslogtreecommitdiff
path: root/doc/faq/operation.html.part
diff options
context:
space:
mode:
authorAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2010-12-07 15:41:44 +0000
committerAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2010-12-07 15:41:44 +0000
commita6813eacb72123966641834799954e4b023d7f75 (patch)
tree86ebaef95704efe14ea79c212c1e5a326f005f49 /doc/faq/operation.html.part
parent738e455a3beaedf5252cb2354381f6facef8d62d (diff)
downloadpaludis-a6813eacb72123966641834799954e4b023d7f75.tar.gz
paludis-a6813eacb72123966641834799954e4b023d7f75.tar.xz
caveify docs
Diffstat (limited to 'doc/faq/operation.html.part')
-rw-r--r--doc/faq/operation.html.part33
1 files changed, 5 insertions, 28 deletions
diff --git a/doc/faq/operation.html.part b/doc/faq/operation.html.part
index ee9a90964..c0845b616 100644
--- a/doc/faq/operation.html.part
+++ b/doc/faq/operation.html.part
@@ -3,8 +3,6 @@
<h1>FAQ: Operation</h1>
<ul>
- <li><a href="operation.html#updatingdepends">Paludis does not update DEPENDs of already installed packages</a></li>
- <li><a href="operation.html#updateworldmissesthings">Updating world misses things</a></li>
<li><a href="operation.html#info">Get package information for a bug report</a></li>
<li><a href="operation.html#arrows">What do those fancy arrows when merging things mean?</a></li>
<li><a href="operation.html#updates">Profiles Updates for Package Moves and Slot Moves</a></li>
@@ -12,37 +10,16 @@
<code>*/*::overlay-&gt;</code></a></li>
</ul>
-<h2 id="updatingdepends">Paludis does not update DEPENDs of already installed packages</h2>
-
-<p>Paludis ignores build time dependencies (DEPENDs) of already installed packages by default.
-If you need a different behaviour, use the <code>--dl-installed-deps-pre</code>
-option. You may also want to use the <code>installed-slots</code> set rather than
-<code>world</code>.</p>
-
-<h2 id="updateworldmissesthings">Updating world misses things</h2>
-
-<p>Paludis doesn't 'miss' packages. If you think it is missing something, check the
-following:</p>
-
-<ul>
- <li>See the previous item. Is the thing in question only included as a build dependency of
- a package?</li>
- <li>Are you sure the package is in world? <code>paludis --query world</code> will tell
- you.</li>
- <li>Is the upgrade being blocked by another package that depends upon a lower version
- of the thing being missed?</li>
-</ul>
-
<h2 id="info">Get package information for a bug report</h2>
-<p>Use <code>paludis --info</code> to get general configuration information. Paludis will <em>not</em> show any
+<p>Use <code>cave info info</code> to get general configuration information. Paludis will <em>not</em> show any
configuration that is 'per-package' in this output. (This is different to <code>emerge</code>, which misleadingly shows
an arbitrary global configuration no matter what.)</p>
-<p>If you are submitting a bug report for a particular package, use <code>paludis --info <em>spec</em></code> instead.
-If it's an installed package, <em>spec</em> can usually just be the qualified package name (for example, <code>paludis
- --info sys-apps/paludis</code>). If you're installing a package, you should instead specify an exact package ID
-(such as <code>paludis --info =sys-apps/paludis-0.26.0_alpha12::paludis-overlay</code>).</p>
+<p>If you are submitting a bug report for a particular package, use <code>cave info <em>spec</em></code> instead.
+If it's an installed package, <em>spec</em> can usually just be the qualified package name (for example, <code>cave
+ info sys-apps/paludis</code>). If you're installing a package, you should instead specify an exact package ID
+(such as <code>cave info =sys-apps/paludis-0.26.0_alpha12::paludis-overlay</code>).</p>
<h2 id="arrows">What do those fancy arrows when merging things mean?</h2>