Attachment 165078 Details for Bug 232903 – hb-install-system.xml.patch

[patch] hb-install-system.xml.patch

hb-install-system.xml.patch (text/plain), 7.35 KB, created by Peter Volkov (RETIRED) on 2008-09-10 07:38:30 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Peter Volkov (RETIRED)

Created: 2008-09-10 07:38:30 UTC

Size: 7.35 KB

patch

obsolete

>Index: hb-install-system.xml
>===================================================================
>RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v
>retrieving revision 1.111
>diff -u -B -r1.111 hb-install-system.xml
>--- hb-install-system.xml	15 May 2008 06:56:48 -0000	1.111
>+++ hb-install-system.xml	10 Sep 2008 07:33:51 -0000
>@@ -189,20 +189,23 @@
> <body>
> 
> 
>-First, a small definition is in place.
>-
>-
>-
>-A profile is a building block for any Gentoo system. Not only does it specify
>-default values for CHOST, CFLAGS and other important variables, it also locks
>-the system to a certain range of package versions. This is all maintained by the
>-Gentoo developers.
>-
>-
>-
>-Previously, such a profile was untouched by the users. However, there may be
>-certain situations in which you may decide a profile change is necessary.
>-
>+A profile is a set of files which specify default values for CHOST, CFLAGS, USE
>+and other important variables, it also locks the system to a certain range of
>+package versions. Gentoo uses cascading profiles. Each file that defines base
>+defaults for your system, like <c>make.defaults</c>, <c>packages</c>, etc. can
>+inherit the contents of like files from parent directories. Files named
>+<c>parent</c> within the selected profile hierarchy specify which directories
>+contain files to use to assemble the final profile. Values specified in files
>+from profile sub-directories take precedence over values specified at a higher
>+level. This is all maintained by the Gentoo developers and you don't need to
>+edit profile files directly but sometimes there may be certain situations in
>+which you may decide a profile change is necessary.
>+
>+
>+<warn>
>+Do <e>not</e> edit the profile files directly. Gentoo provides other means to 
>+customize and extend these settings.
>+</warn>
> 
> 
> You can see what profile you are currently using with the following command:
>Index: hb-portage-configuration.xml
>===================================================================
>RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-configuration.xml,v
>retrieving revision 1.17
>diff -u -B -r1.17 hb-portage-configuration.xml
>--- hb-portage-configuration.xml	28 Feb 2008 08:25:26 -0000	1.17
>+++ hb-portage-configuration.xml	10 Sep 2008 07:33:51 -0000
>@@ -48,7 +48,7 @@
> <ul>
> <li>
> CFLAGS &amp; CXXFLAGS define the desired compiler flags for C and C++
>- compiling.
>+ compiling
> </li>
> <li>
> CHOST defines the build host information for the application's configure 
>@@ -57,7 +57,7 @@
> <li>
> MAKEOPTS is passed to the <c>make</c> command and is usually set to define
> the amount of parallelism used during the compilation. More information
>- about the make options can be found in the <c>make</c> man page.
>+ about the make options can be found in the <c>make</c> man page
> </li>
> </ul>
> 
>@@ -153,8 +153,8 @@
> 
> <ul>
> <li>
>- GENTOO_MIRRORS defines a list of server locations which
>- contain source code (distfiles)
>+ GENTOO_MIRRORS defines a list of server locations which contain source code
>+ (distfiles)
> </li>
> <li>
> PORTAGE_BINHOST defines a particular server location containing prebuilt
>@@ -233,17 +233,17 @@
> PORTAGE_RSYNC_OPTS sets a number of default variables used during sync,
> each space-separated. These shouldn't be changed unless you know
> <e>exactly</e> what you're doing. Note that certain absolutely required
>- options will always be used even if PORTAGE_RSYNC_OPTS is empty.
>+ options will always be used even if PORTAGE_RSYNC_OPTS is empty
> </li>
> <li>
> PORTAGE_RSYNC_EXTRA_OPTS can be used to set additional options when
>- syncing. Each option should be space separated.
>+ syncing. Each option should be space separated
> <ul>
> <li>
> 	--timeout=&lt;number&gt;: This defines the number of seconds an rsync
> 	connection can idle before rsync sees the connection as timed-out. This
> 	variable defaults to 180 but dialup users or individuals with slow
>-	computers might want to set this to 300 or higher.
>+	computers might want to set this to 300 or higher
> </li>
> <li>
> 	--exclude-from=/etc/portage/rsync_excludes: This points to a file
>@@ -251,7 +251,7 @@
> 	update process. In this case, it points to
> 	<path>/etc/portage/rsync_excludes</path>. Please read <uri
> 	link="?part=3&amp;chap=5">Using a Portage Tree Subset</uri> for the
>-	syntax of this file.
>+	syntax of this file
> </li>
> <li>--quiet: Reduces output to the screen</li>
> <li>--verbose: Prints a complete filelist</li>
>@@ -261,7 +261,7 @@
> <li>
> PORTAGE_RSYNC_RETRIES defines how many times rsync should try connecting to
> the mirror pointed to by the SYNC variable before bailing out. This
>- variable defaults to 3.
>+ variable defaults to 3
> </li>
> </ul>
> 
>Index: hb-portage-files.xml
>===================================================================
>RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-files.xml,v
>retrieving revision 1.19
>diff -u -B -r1.19 hb-portage-files.xml
>--- hb-portage-files.xml	17 Apr 2008 21:21:14 -0000	1.19
>+++ hb-portage-files.xml	10 Sep 2008 07:33:51 -0000
>@@ -313,30 +313,30 @@
> <ul>
> <li>
> 	<c>save</c>: This saves one log per package in
>-	<path>$PORT_LOGDIR/elog</path>, or <path>/var/log/portage/elog</path> if
>-	$PORT_LOGDIR is not defined.
>+	<path>$PORT_LOGDIR/elog/</path>, or <path>/var/log/portage/elog/</path>
>+	if $PORT_LOGDIR is not defined
> </li>
> <li>
> 	<c>custom</c>: Passes all messages to a user-defined command in
>-	$PORTAGE_ELOG_COMMAND; this will be discussed later.
>+	$PORTAGE_ELOG_COMMAND; this will be discussed later
> </li>
> <li>
>-	<c>syslog</c>: Sends all messages to the installed system logger.
>+	<c>syslog</c>: Sends all messages to the installed system logger
> </li>
> <li>
> 	<c>mail</c>: Passes all messages to a user-defined mailserver in
> 	$PORTAGE_ELOG_MAILURI; this will be discussed later. The mail features
>-	of elog require &gt;=<c>portage-2.1.1</c>.
>+	of elog require &gt;=<c>portage-2.1.1</c>
> </li>
> <li>
> 	<c>save_summary</c>: Similar to <c>save</c>, but it merges all messages
> 	in <path>$PORT_LOGDIR/elog/summary.log</path>, or
> 	<path>/var/log/portage/elog/summary.log</path> if $PORT_LOGDIR is not
>-	defined.
>+	defined
> </li>
> <li>
> 	<c>mail_summary</c>: Similar to <c>mail</c>, but it sends all messages
>-	in a single mail when emerge exits.
>+	in a single mail when emerge exits
> </li>
> </ul>
> </li>
>@@ -355,7 +355,7 @@
> <li>
> PORTAGE_ELOG_MAILURI: This contains settings for the <c>mail</c> module
> such as address, user, password, mailserver, and port number. The default
>- setting is "root@localhost localhost".
>+ setting is "root@localhost localhost"
> </li>
> <li>
> Here's an example for an smtp server that requires username and
>@@ -370,13 +370,13 @@
> </li>
> <li>
> PORTAGE_ELOG_MAILFROM: Allows you to set the "from" address of log mails;
>- defaults to "portage" if unset.
>+ defaults to "portage" if unset
> </li>
> <li>
> PORTAGE_ELOG_MAILSUBJECT: Allows you to create a subject line for log
> mails. Note that you can make use of two variables: ${PACKAGE} will display
> the package name and version, while ${HOST} is the fully qualified domain
>- name of the host Portage is running on.
>+ name of the host Portage is running on
> </li>
> <li>
> Here's one possible use:

Actions: View | Diff

Attachments on bug 232903: 162419 | 165078 | 188630