diff options
authorAvatar Richard Brown <rbrown@exherbo.org> 2007-01-17 07:57:44 +0000
committerAvatar Richard Brown <rbrown@exherbo.org> 2007-01-17 07:57:44 +0000
commitf70f2095b708b515e397c42c3331111f34b56c08 (patch)
parent23abb96bd856b730aedbcfb2f493f218d126b4ab (diff)
Docs Fix
4 files changed, 5 insertions, 5 deletions
diff --git a/doc/cachefiles.html.skel b/doc/cachefiles.html.skel
index db2d308..55f6f29 100644
--- a/doc/cachefiles.html.skel
+++ b/doc/cachefiles.html.skel
@@ -83,7 +83,7 @@ cache may not be available.</p>
<p>Paludis can generate metadata cache locally on demand. This will not speed up the
first time cache is accessed for a particular ebuild, but subsequent invocations
will be several orders of magnitude faster. To enable this cache where it is needed,
-set the <code>write_cache</code> key in a Portage format repository. Recommended
+set the <code>write_cache</code> key in an ebuild format repository. Recommended
values are <code>/var/cache/paludis/metadata</code> or
<code>/home/username/.paludis-cache</code>. Note that Paludis will place the
write cache for a repository into a subdirectory named for that repository, so
diff --git a/doc/faq.html.skel b/doc/faq.html.skel
index 06b9bcc..624b3ee 100644
--- a/doc/faq.html.skel
+++ b/doc/faq.html.skel
@@ -393,7 +393,7 @@ a rather ugly way of handling things. We do have equivalents to most values:</p>
<h3 id="profiles">Profiles vs Profiles</h3>
<p>Don't confuse the <code>profiles/</code> directory with the <code>profiles
- =</code> setting for Portage format repositories. The special files
+ =</code> setting for ebuild format repositories. The special files
immediately under <code>profiles/</code>, such as
<code>profiles/thirdpartymirrors</code>, <code>profiles/use.desc</code>
and <code>profiles/package.mask</code>, are specific to that particular profile
@@ -407,7 +407,7 @@ peanut gallery, repositories are required to be uniquely identifiable. The
identifier must remain consistent even if a repository is moved, either locally
or remotely, and thus must be independent of user configuration.</p>
-<p>For Portage format repositories, this is controlled by the <code>profiles/repo_name</code>
+<p>For ebuild format repositories, this is controlled by the <code>profiles/repo_name</code>
file. It should contain a single string with no whitespace or funny characters.
For many repositories, this has already been created for you; for some overlays,
probably including your local overlay if you have one, the file is not yet
diff --git a/doc/migration.html.skel b/doc/migration.html.skel
index 9aa84b2..442a7d6 100644
--- a/doc/migration.html.skel
+++ b/doc/migration.html.skel
@@ -131,7 +131,7 @@ END
<code>/usr/portage</code> for the main tree because sticking data that gets
changed on <code>/usr</code> is silly.</p>
-<p>You will also need to specify <code>names_cache</code> for the Portage format
+<p>You will also need to specify <code>names_cache</code> for the ebuild format
repositories and <code>provides_cache</code> for the VDB repositories.
See <a href="cachefiles.html">the cache documentation</a>.</p>
diff --git a/doc/sets.html.skel b/doc/sets.html.skel
index 6436a95..600471e 100644
--- a/doc/sets.html.skel
+++ b/doc/sets.html.skel
@@ -67,7 +67,7 @@ in which <code>use.conf</code> et al. reside. The format is as follows:</p>
<h3>Portage Repositories Defined Sets</h3>
-<p>Portage format repositories can supply their own sets. The <code>system</code> and
+<p>Ebuild format repositories can supply their own sets. The <code>system</code> and
<code>security</code> sets are defined programmatically; other sets are defined by a file
named <code>sets/<em>setname</em>.conf</code>, which should be in the format described for
user defined sets above.</p>