diff options
authorAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2011-06-11 23:42:12 +0100
committerAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2011-06-11 23:42:12 +0100
commite379672bd8a1167080b362974cea1820ace4a5ba (patch)
parentec6c509724ed7a62bfc4376c6856943dcbe45720 (diff)
Undocument virtuals
3 files changed, 0 insertions, 25 deletions
diff --git a/doc/configuration/repositories/index.html.part b/doc/configuration/repositories/index.html.part
index 169c051..9abc880 100644
--- a/doc/configuration/repositories/index.html.part
+++ b/doc/configuration/repositories/index.html.part
@@ -74,19 +74,6 @@ other keys.</p>
<li><a href="vdb.html">VDB</a>, for tracking installed ebuilds.</li>
-<p>In addition, the following repositories are magically defined on Gentoo and derived distributions that make use of
-old-style virtuals:</p>
- <dt><code>virtuals</code></dt>
- <dd>A special repository that contains special package entries for old style virtuals, mapping them to their
- providers.</dd>
- <dt><code>installed-virtuals</code></dt>
- <dd>A special repository that contains special package entries for installed old style virtuals (provided
- packages).</dd>
diff --git a/doc/configuration/repositories/vdb.html.part b/doc/configuration/repositories/vdb.html.part
index 722c7b1..4fa8fe2 100644
--- a/doc/configuration/repositories/vdb.html.part
+++ b/doc/configuration/repositories/vdb.html.part
@@ -13,11 +13,6 @@ for <code>vdb</code> format repositories:</p>
<dd>The location of the repository. Mandatory. On Gentoo systems, this must be <code>${root}/var/db/pkg</code> to
avoid problems with broken ebuilds that illegally access the VDB.</dd>
- <dt><code>provides_cache</code></dt>
- <dd>The file to use for reading and writing a cache of providers of old-style virtuals. See <a
- href="../../overview/gettingstarted.html">Getting Started</a> for notes. Optional, set to <code>/var/empty</code>
- to disable.</dd>
<dd>The directory in which to look for a names cache, and in which to generate a names cache. A names cache will
significantly speed up converting a <code>pkg</code> into a <code>cat/pkg</code>. See <a
diff --git a/doc/overview/gettingstarted.html.part b/doc/overview/gettingstarted.html.part
index dd81989..186f5fb 100644
--- a/doc/overview/gettingstarted.html.part
+++ b/doc/overview/gettingstarted.html.part
@@ -229,7 +229,6 @@ via <code>--sync</code>) modify a repository.</p>
location = /var/db/pkg/
format = vdb
names_cache = (see below)
-provides_cache = (see below)
<p>The <code>names_cache = </code> option, if set to (for example) <code>/var/cache/paludis/names</code>, can be used to
@@ -238,12 +237,6 @@ seconds on typical hardware). Most users will benefit hugely from this option. H
this cache, so if for any reason you use Portage for any operation, you must then run <code>cave
-<p>The <code>provides_cache = </code> option, if set to (for example) <code>/var/cache/paludis/provides</code>, can be
-used to make resolving an old style virtual to its providers much faster (a lot less of a second, as opposed to anywhere
-up to a minute if many packages are installed). Because many common operations require a virtual resolution, using this
-option can give huge speedups. Again, however, Portage will not use this cache, so you will need to regenerate it
-manually if you install or uninstall any package using Portage.</p>
<p>To disable either cache, use <code>/var/empty</code> as the value.</p>
<p>You are responsible for ensuring that any cache directories you use exist and have appropriate permissions.</p>