|author||Zac Medico <firstname.lastname@example.org>||2018-08-06 16:38:55 -0700|
|committer||Zac Medico <email@example.com>||2018-08-06 16:38:55 -0700|
|parent||repoman: remove obsolete herds checks (diff)|
Refer to "ebuild repository" rather than "portage tree"
Diffstat (limited to 'man')
3 files changed, 9 insertions, 9 deletions
diff --git a/man/emerge.1 b/man/emerge.1
index f53ba92f5..08d23388d 100644
@@ -22,7 +22,7 @@ emerge \- Command\-line interface to the Portage system
\fBemerge\fR is the definitive command\-line interface to the Portage
system. It is primarily used for installing packages, and \fBemerge\fR
can automatically handle any dependencies that the desired package has.
-\fBemerge\fR can also update the \fBportage tree\fR, making new and
+\fBemerge\fR can also update the \fBebuild repository\fR, making new and
updated packages available. \fBemerge\fR gracefully handles updating
installed packages to newer releases as well. It handles both source
and binary packages, and it can be used to create binary packages for
@@ -198,7 +198,7 @@ the emerge output of the next \-\-depclean run carefully! Use
Causes portage to check and update the dependency cache of all ebuilds in the
-portage tree. The cache is used to speed up searches and the building of
+repository. The cache is used to speed up searches and the building of
dependency trees. This command is not recommended for rsync users as rsync
updates the cache using server\-side caches. If you do not know the
differences between a 'rsync user' and some other user, then you are a 'rsync
@@ -227,7 +227,7 @@ explicitly discarded by running `emaint \-\-fix cleanresume` (see
.BR \-\-search ", " \-s
-Searches for matches of the supplied string in the portage tree.
+Searches for matches of the supplied string in the ebuild repository.
By default emerge uses a case-insensitive simple search, but you can
enable a regular expression search by prefixing the search string with %.
For example, \fBemerge \-\-search "%^kde"\fR searches for any package whose
@@ -264,7 +264,7 @@ more information about sync operations.
The \fBemerge\-webrsync\fR program will download the entire
-portage tree as a tarball, which is much faster than emerge
+ebuild repository as a tarball, which is much faster than emerge
\-\-sync for first time syncs.
@@ -1230,7 +1230,7 @@ You should almost always precede any package install or update attempt with a
\fB\-\-pretend\fR install or update. This lets you see how much will be
done, and shows you any blocking packages that you will have to rectify.
This goes doubly so for the \fBsystem\fR and \fBworld\fR sets, which can
-update a large number of packages if the portage tree has been particularly
+update a large number of packages if the ebuild repository has been particularly
You also want to typically use \fB\-\-update\fR, which ignores packages that
diff --git a/man/make.conf.5 b/man/make.conf.5
index a4e33923c..a33929143 100644
@@ -1101,7 +1101,7 @@ Defaults to /usr/portage/rpm.
\fBSYNC\fR = \fI[RSYNC]\fR
Insert your preferred rsync mirror here. This rsync server
-is used to sync the local portage tree when `emerge \-\-sync` is run.
+is used to sync the local ebuild repository when `emerge \-\-sync` is run.
Note that the \fBSYNC\fR variable is now deprecated, and instead the
sync\-type and sync\-uri attributes in repos.conf should be used. See
diff --git a/man/portage.5 b/man/portage.5
index cd9d5036d..c3c610a6c 100644
@@ -214,7 +214,7 @@ More reading:
\fB/etc/portage/make.profile/\fR or \fB/etc/make.profile/\fR
This is usually just a symlink to the correct profile in
-\fB/usr/portage/profiles/\fR. Since it is part of the portage tree, it
+\fB/usr/portage/profiles/\fR. Since it is part of the ebuild repository, it
may easily be updated/regenerated by running `emerge \-\-sync`. It defines
what a profile is (usually arch specific stuff). If you need a custom
profile, then you should make your own \fBmake.profile\fR
@@ -1666,13 +1666,13 @@ again.
All installed package information is recorded here. If portage thinks you have
a package installed, it is usually because it is listed here.
-The format follows somewhat closely that of the portage tree. There is a
+The format follows somewhat closely that of the ebuild repository. There is a
directory for each category and a package-version subdirectory for each package
you have installed.
Inside each package directory are misc files that describe the installed
contents of the package as well as build time information (so that the package
-can be unmerged without needing the portage tree).
+can be unmerged without needing the ebuild repository).
The exact file contents and format are not described here again so that things
can be changed quickly. Generally though there is one file per environment