From cb078394988d60e5ff231712163255abebc2fc22 Mon Sep 17 00:00:00 2001 From: Alexander Berntsen Date: Tue, 30 Jul 2013 20:53:51 +0200 Subject: man: Remove trailing spaces --- man/portage.5 | 152 +++++++++++++++++++++++++++++----------------------------- 1 file changed, 76 insertions(+), 76 deletions(-) (limited to 'man/portage.5') diff --git a/man/portage.5 b/man/portage.5 index 827c50402..38c6d8ca3 100644 --- a/man/portage.5 +++ b/man/portage.5 @@ -2,16 +2,16 @@ .SH NAME portage \- the heart of Gentoo .SH "DESCRIPTION" -The current portage code uses many different configuration files, most of which -are unknown to users and normal developers. Here we will try to collect all -the odds and ends so as to help users more effectively utilize portage. This +The current portage code uses many different configuration files, most of which +are unknown to users and normal developers. Here we will try to collect all +the odds and ends so as to help users more effectively utilize portage. This is a reference only for files which do not already have a man page. -All files in the make.profile directory may be tweaked via parent profiles -when using cascading profiles. For more info, please see +All files in the make.profile directory may be tweaked via parent profiles +when using cascading profiles. For more info, please see http://www.gentoo.org/proj/en/releng/docs/cascading-profiles.xml .IP Note: -If you are looking for information on how to emerge something, please see +If you are looking for information on how to emerge something, please see .BR emerge (1). .SH "SYNOPSIS" .TP @@ -122,8 +122,8 @@ world world_sets .fi .SH "GLOSSARY" -In the following sections, some terminology may be foreign to you or used -with meaning specific to Portage. Please see the referenced manpages for +In the following sections, some terminology may be foreign to you or used +with meaning specific to Portage. Please see the referenced manpages for more detailed explanations. .RS .TP @@ -132,7 +132,7 @@ An atom is either of the form category/package or consists of an operator followed by category/package followed by a hyphen and a version specification. An atom might be suffixed by a slot specification. .br -More reading: +More reading: .BR ebuild (5) .B Extended Atom Syntax @@ -188,26 +188,26 @@ net\-*/* .B KEYWORD Each architecture has a unique KEYWORD. .br -More reading: +More reading: .BR ebuild (5) .TP .B virtual -A DEPEND atom that is part of the "virtual" category. They are used -when different packages can satisfy a dependency and only one of them is +A DEPEND atom that is part of the "virtual" category. They are used +when different packages can satisfy a dependency and only one of them is needed. .br -More reading: +More reading: .BR ebuild (5) .RE .SH "SPECIFIC FILE DESCRIPTIONS" .TP \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 -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 -directory and populate it. However, if you just wish to override some +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 +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 +directory and populate it. However, if you just wish to override some settings, use \fB/etc/portage/profile/\fR (it supports all of the same file types that \fBmake.profile\fR does, except parent). Do NOT edit the settings in \fBmake.profile\fR because they WILL be lost with the next @@ -230,9 +230,9 @@ ${PORTDIR}/profiles/package.mask/testing .RS .TP .BR deprecated -The existence of this file marks a profile as deprecated, meaning it is -not supported by Gentoo anymore. The first line must be the profile to which -users are encouraged to upgrade, optionally followed by some instructions +The existence of this file marks a profile as deprecated, meaning it is +not supported by Gentoo anymore. The first line must be the profile to which +users are encouraged to upgrade, optionally followed by some instructions explaining how they can upgrade. .I Example: @@ -255,8 +255,8 @@ previously supported USE configuration files, except that they only influence packages that are merged due to a stable keyword. .TP .BR make.defaults -The profile default settings for Portage. The general format is described -in \fBmake.conf\fR(5). The \fImake.defaults\fR for your profile defines a +The profile default settings for Portage. The general format is described +in \fBmake.conf\fR(5). The \fImake.defaults\fR for your profile defines a few specific variables too: .PD 0 @@ -317,11 +317,11 @@ Defines USERLAND values used to generate implicit Support uClibc/BSD libc/etc... .TP .B PROFILE_ONLY_VARIABLES = \fI"ARCH"\fR -Prevent critical variables from being changed by the user in make.conf +Prevent critical variables from being changed by the user in make.conf or the env. .TP .BR PROFILE_ARCH -Distinguish machines classes that have the same \fBARCH\fR. All sparc +Distinguish machines classes that have the same \fBARCH\fR. All sparc machines have ARCH=sparc but set this to either 'sparc32' or 'sparc64'. .TP .BR BOOTSTRAP_USE @@ -340,8 +340,8 @@ Provides the list of packages that compose the special \fIsystem\fR set. \- atoms without * only appear for legacy reasons .fi .I Note: -In a cascading profile setup, you can remove packages in children -profiles which were added by parent profiles by prefixing the atom with +In a cascading profile setup, you can remove packages in children +profiles which were added by parent profiles by prefixing the atom with a '\-'. .I Example: @@ -356,16 +356,16 @@ a '\-'. .fi .TP .BR packages.build -A list of packages (one per line) that make up a stage1 tarball. Really only +A list of packages (one per line) that make up a stage1 tarball. Really only useful for stage builders. .TP .BR package.provided -A list of packages (one per line) that portage should assume have been +A list of packages (one per line) that portage should assume have been provided. Useful for porting to non-Linux systems. Basically, it's a list that replaces the \fBemerge \-\-inject\fR syntax. -For example, if you manage your own copy of a 2.6 kernel, then you can -tell portage that 'sys-kernel/development-sources-2.6.7' is already taken +For example, if you manage your own copy of a 2.6 kernel, then you can +tell portage that 'sys-kernel/development-sources-2.6.7' is already taken care of and it should get off your back about it. Portage will not attempt to update a package that is listed here unless @@ -406,8 +406,8 @@ x11-base/xorg-x11-6.8 Per\-package USE flag forcing. .I Note: -In a cascading profile setup, you can remove USE flags in children -profiles which were added by parent profiles by prefixing the flag with +In a cascading profile setup, you can remove USE flags in children +profiles which were added by parent profiles by prefixing the flag with a '\-'. .I Format: @@ -428,8 +428,8 @@ x11\-libs/qt \-mysql Per\-package USE flag masks. .I Note: -In a cascading profile setup, you can remove USE flags in children -profiles which were added by parent profiles by prefixing the flag with +In a cascading profile setup, you can remove USE flags in children +profiles which were added by parent profiles by prefixing the flag with a '\-'. .I Format: @@ -470,8 +470,8 @@ Some USE flags don't make sense to disable under certain conditions. Here we list forced flags. .I Note: -In a cascading profile setup, you can remove USE flags in children -profiles which were added by parent profiles by prefixing the flag with +In a cascading profile setup, you can remove USE flags in children +profiles which were added by parent profiles by prefixing the flag with a '\-'. .I Format: @@ -481,13 +481,13 @@ a '\-'. .fi .TP \fBuse.mask\fR and \fBuse.stable.mask\fR -Some USE flags don't make sense on some archs (for example altivec on -non\-ppc or mmx on non\-x86), or haven't yet been tested. Here we list +Some USE flags don't make sense on some archs (for example altivec on +non\-ppc or mmx on non\-x86), or haven't yet been tested. Here we list the masked ones. .I Note: -In a cascading profile setup, you can remove USE flags in children -profiles which were added by parent profiles by prefixing the flag with +In a cascading profile setup, you can remove USE flags in children +profiles which were added by parent profiles by prefixing the flag with a '\-'. .I Format: @@ -529,8 +529,8 @@ virtual/aspell\-dict app\-dicts/aspell\-en .RE .TP .BR /etc/portage/ -Any file in this directory that begins with "package." can be more than just a -flat file. If it is a directory, then all the files in that directory will be +Any file in this directory that begins with "package." can be more than just a +flat file. If it is a directory, then all the files in that directory will be sorted in ascending alphabetical order by file name and summed together as if it were a single file. @@ -550,8 +550,8 @@ any other bash script. Additional package-specific bashrc files can be created in /etc/portage/env. .TP .BR categories -A simple list of valid categories that may be used in /usr/portage, -PORTDIR_OVERLAY, and PKGDIR (see \fBmake.conf\fR(5)). This allows for custom +A simple list of valid categories that may be used in /usr/portage, +PORTDIR_OVERLAY, and PKGDIR (see \fBmake.conf\fR(5)). This allows for custom categories to be created. .I Format: @@ -572,11 +572,11 @@ Contains variables customizing colors. See \fBcolor.map\fR(5). The global custom settings for Portage. See \fBmake.conf\fR(5). .TP .BR mirrors -Whenever portage encounters a mirror:// style URI it will look up the actual -hosts here. If the mirror set is not found here, it will check the global -mirrors file at /usr/portage/profiles/thirdpartymirrors. You may also set a -special mirror type called "local". This list of mirrors will be checked -before GENTOO_MIRRORS and will be used even if the package has +Whenever portage encounters a mirror:// style URI it will look up the actual +hosts here. If the mirror set is not found here, it will check the global +mirrors file at /usr/portage/profiles/thirdpartymirrors. You may also set a +special mirror type called "local". This list of mirrors will be checked +before GENTOO_MIRRORS and will be used even if the package has RESTRICT="mirror" or RESTRICT="fetch". .I Format: @@ -654,8 +654,8 @@ three special tokens: .fi .I Additional Note: -If you encounter the \fB-*\fR KEYWORD, this indicates that the package is known -to be broken on all systems which are not otherwise listed in KEYWORDS. For +If you encounter the \fB-*\fR KEYWORD, this indicates that the package is known +to be broken on all systems which are not otherwise listed in KEYWORDS. For example, a binary only package which is built for x86 will look like: games-fps/quake3-demo-1.11.ebuild:KEYWORDS="-* x86" @@ -735,15 +735,15 @@ a single package. .fi .TP .BR package.unmask -Just like package.mask above, except here you list packages you want to -unmask. Useful for overriding the global package.mask file (see -above). Note that this does not override packages that are masked via +Just like package.mask above, except here you list packages you want to +unmask. Useful for overriding the global package.mask file (see +above). Note that this does not override packages that are masked via KEYWORDS. .TP .BR package.use -Per\-package USE flags. Useful for tracking local USE flags or for -enabling USE flags for certain packages only. Perhaps you develop GTK -and thus you want documentation for it, but you don't want +Per\-package USE flags. Useful for tracking local USE flags or for +enabling USE flags for certain packages only. Perhaps you develop GTK +and thus you want documentation for it, but you don't want documentation for QT. Easy as pie my friend! .I Format: @@ -1040,7 +1040,7 @@ profile\-formats = portage-2 .RE .TP .BR /usr/portage/profiles/ -Global Gentoo settings that are controlled by the developers. To override +Global Gentoo settings that are controlled by the developers. To override these settings, you can use the files in \fB/etc/portage/\fR. .RS .TP @@ -1060,7 +1060,7 @@ sparc .fi .TP .BR categories -A simple list of valid categories that may be used in /usr/portage, +A simple list of valid categories that may be used in /usr/portage, PORTDIR_OVERLAY, and PKGDIR (see \fBmake.conf\fR(5)). .I Format: @@ -1130,10 +1130,10 @@ net-analyzer/netcat -* .fi .TP .BR package.mask -This contains a list of DEPEND atoms for packages that should not be installed -in any profile. Useful for adding the latest KDE betas and making sure no -one accidentally upgrades to them. Also useful for quickly masking specific -versions due to security issues. ALWAYS include a comment explaining WHY the +This contains a list of DEPEND atoms for packages that should not be installed +in any profile. Useful for adding the latest KDE betas and making sure no +one accidentally upgrades to them. Also useful for quickly masking specific +versions due to security issues. ALWAYS include a comment explaining WHY the package has been masked and WHO is doing the masking. .I Format: @@ -1153,7 +1153,7 @@ package has been masked and WHO is doing the masking. .fi .TP .BR profiles.desc -List all the current stable and development profiles. If a profile is listed +List all the current stable and development profiles. If a profile is listed here, then it will be checked by repoman. .I Format: .nf @@ -1179,7 +1179,7 @@ hyphen. If the repo\-name attribute is specified in layout.conf, then that setting will take precedence. .TP .BR thirdpartymirrors -Controls the mapping of mirror:// style URIs to actual lists of +Controls the mapping of mirror:// style URIs to actual lists of mirrors. Keeps us from overloading a single server. .I Format: @@ -1200,7 +1200,7 @@ kernel http://www.kernel.org/pub http://www.us.kernel.org/pub .fi .TP .BR use.desc -All global USE flags must be listed here with a description of what they do. +All global USE flags must be listed here with a description of what they do. .I Format: .nf @@ -1216,7 +1216,7 @@ doc \- Adds extra documentation .fi .TP .BR use.local.desc -All local USE flags are listed here along with the package and a +All local USE flags are listed here along with the package and a description. This file is automatically generated from the metadata.xml files that are included with each individual package. Refer to GLEP 56 for further information: @@ -1238,7 +1238,7 @@ games\-emulation/xmess:net \- Adds network support .RS .TP .BR make.globals -The global default settings for Portage. This comes from the portage package +The global default settings for Portage. This comes from the portage package itself. Settings in \fBmake.conf\fR or \fBpackage.env\fR override values set here. The format is described extensively in \fBmake.conf\fR(5). .TP @@ -1290,12 +1290,12 @@ directories have been modified since being installed. Files which have not been modified will automatically be unmerged. .TP .BR world -Every time you emerge a package, the package that you requested is -recorded here. Then when you run `emerge world \-up`, the list of -packages is read from this file. Note that this does not mean that the -packages that were installed as dependencies are listed here. For -example, if you run `emerge mod_wsgi` and you do not have apache -already, then "www\-apache/mod_wsgi" is recorded in the world file but +Every time you emerge a package, the package that you requested is +recorded here. Then when you run `emerge world \-up`, the list of +packages is read from this file. Note that this does not mean that the +packages that were installed as dependencies are listed here. For +example, if you run `emerge mod_wsgi` and you do not have apache +already, then "www\-apache/mod_wsgi" is recorded in the world file but "www\-servers/apache" is not. For more information, review \fBemerge\fR(1). .I Format: -- cgit v1.2.3-65-gdbad