[gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: bootstrap-macos.xml

[Fabian Groffen (grobian)]

grobian     08/02/21 17:13:39

  Modified:             bootstrap-macos.xml
  Log:
  Capitalise occurrences of Prefix

Revision  Changes    Path
1.27                 xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml?rev=1.27&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml?rev=1.27&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml?r1=1.26&r2=1.27

Index: bootstrap-macos.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- bootstrap-macos.xml	21 Feb 2008 16:46:27 -0000	1.26
+++ bootstrap-macos.xml	21 Feb 2008 17:13:38 -0000	1.27
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml,v 1.26 2008/02/21 16:46:27 grobian Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml,v 1.27 2008/02/21 17:13:38 grobian Exp $ -->
 
 <guide link="/proj/en/gentoo-alt/prefix/bootstrap-macos.xml" lang="en">
   <title>Gentoo Prefixed Portage Bootstrap Process for Mac OS X</title>
@@ -32,7 +32,7 @@
           Apple Mac OS X was initially supported in the main Gentoo
           portage tree with the ppc-macos keyword.  The approach taken
           then, however, resulted in too many problems, which was the
-          drive behind creating prefixed portage.
+          drive behind creating Prefixed Portage.
         </p>
         <p>
           Bootstrapping on OS X is relatively simple, as the system
@@ -57,8 +57,8 @@
         </p>
         <p>
           The first step is to choose a path to install into.  We refer
-          to this path as "prefix path", stored in the variable
-          <c>EPREFIX</c>.  Some suggestions for your prefix path are
+          to this path as "Prefix path", stored in the variable
+          <c>EPREFIX</c>.  Some suggestions for your Prefix path are
           <path>$HOME/Gentoo</path> or <path>$HOME/Library/Gentoo</path>.
           Whatever you chose, make sure you set it in your environment:
         </p>
@@ -70,7 +70,7 @@
           instead.
         </note>
         <p>
-          Next, add the following paths in your soon to be prefix to
+          Next, add the following paths in your soon to be Prefix to
           your <c>PATH</c> environment.
           <path>$EPREFIX/bin</path>,
           <path>$EPREFIX/usr/bin</path>,
@@ -79,7 +79,7 @@
           Adding these paths makes sure that they will be available
           later on in the process.
         </p>
-        <pre caption="Add prefix paths to your PATH">
+        <pre caption="Add Prefix paths to your PATH">
 $ <i>export PATH="$EPREFIX/usr/bin:$EPREFIX/bin:$EPREFIX/tmp/usr/bin:$EPREFIX/tmp/bin:$PATH"</i>
         </pre>
         <p>
@@ -141,18 +141,18 @@
         </pre>
         <p>
           Next, we emerge the <c>bash</c> shell Portage heavily relies
-          on.  Since its dependencies cannot be compiled at this stage,
-          we ignore those for the moment.  The same holds for
-          <c>wget</c> which we emerge at the same time.
+          on.  The same holds for <c>wget</c>, the download manager.
+          Since its dependencies cannot be compiled at this stage,
+          we ignore those for the moment.
         </p>
         <pre caption="emerge bash and wget">
-$ <i>emerge --oneshot --nodeps "&lt;bash-3.2_p33"</i>
+$ <i>emerge --oneshot "&lt;bash-3.2_p33"</i>
 $ <i>emerge --oneshot --nodeps wget</i>
         </pre>
         <p>
-          We continue getting more tools in our prefix.  We no longer
+          We continue getting more tools in our Prefix.  We no longer
           ignore dependencies, so a lot of packages will be emerged at
-          this stage.  Slowly our prefix gets more robust as we progress
+          this stage.  Slowly our Prefix gets more robust as we progress
           here.
         </p>
         <pre caption="emerge several tools">
@@ -165,8 +165,10 @@
         <p>
           Now we have a good bunch of programs that Portage needs, we
           can replace the bootstrapped Portage by a properly installed
-          one, using portage itself.  We need to temporarily tell
-          Portage that the bootstrapped Portage can be overwritten.
+          one, using portage itself.  Also here a few dependencies are
+          first emerged, such as the language Portage is written in:
+          <c>python</c>.  We need to temporarily tell Portage that the
+          bootstrapped Portage can be overwritten.
         </p>
         <pre caption="emerge portage">
 $ <i>env FEATURES="-collision-protect" emerge --oneshot portage</i>
@@ -191,7 +193,7 @@
         </pre>
         <p>
           Before we do any further merges, we are going to update our
-          tree.  Since snapshots in prefix are actually (anonymous) SVN
+          tree.  Since snapshots in Prefix are actually (anonymous) SVN
           checkouts of the tree, we need <c>subversion</c> to update it.
         </p>
         <pre caption="emerge subversion">
@@ -207,15 +209,15 @@
 $ <i>emerge --sync</i>
         </pre>
         <note>
-          The prefix portage tree assumes a <e>case-sensitive
+          The Prefix Portage tree assumes a <e>case-sensitive
             filesystem</e>.  Mac OS X doesn't use this by default.  If
           you experience weird errors while updating or checking out
-          the prefix tree with subversion, check if your filesystem is
+          the Prefix tree with subversion, check if your filesystem is
           case-sensitive.
         </note>
         <p>
           Next, we let Portage emerge all packages that complete a
-          system install that we eventually need to finalise this prefix
+          system install that we eventually need to finalise this Prefix
           installation.
         </p>
         <pre caption="emerge system">
@@ -223,13 +225,13 @@
         </pre>
         <p>
           Now is a good time to set the preferences for our soon to be
-          prefix.  This includes customisations such as general
+          Prefix.  This includes customisations such as general
           <c>USE</c>-flags, <c>CFLAGS</c> and <c>MAKEOPTS</c> in
           <path>$EPREFIX/etc/make.conf</path>.  Be conservative with
           <c>CFLAGS</c>!  Note that the code below is an example, and is
           meant for inspiration only.
         </p>
-        <pre caption="Customising the prefix installation - example">
+        <pre caption="Customising the Prefix installation - example">
 $ <i>echo 'USE="unicode nls"' >> $EPREFIX/etc/make.conf</i>
 $ <i>echo 'CFLAGS="-O2 -pipe &lt;my-cpu-flags&gt;"' >> $EPREFIX/etc/make.conf</i>
 $ <i>echo 'CXXFLAGS="${CFLAGS}"' >> $EPREFIX/etc/make.conf</i>
@@ -247,9 +249,9 @@
         <p>
           Since we have everything in place for a self-catered rebuild,
           we can unset all hacks we made to help the bootstrap process,
-          and start the final stage to install the prefix system.  This
+          and start the final stage to install the Prefix system.  This
           final stage recompiles everything in the system, but now all
-          packages can be compiled with tools from the prefix, instead
+          packages can be compiled with tools from the Prefix, instead
           of those from the host system.
         </p>
         <pre caption="Unsetting LDFLAGS and CPPFLAGS variables">
@@ -262,9 +264,9 @@
           <c>CPPFLAGS</c>.
         </note>
         <p>
-          After <c>system</c> has emerged successfully, your prefix will
+          After <c>system</c> has emerged successfully, your Prefix will
           be set up properly, and you can emerge the whichever tools you
-          choose from the prefix tree.
+          choose from the Prefix tree.
         </p>
       </body>
     </section><!-- }}} -->
@@ -273,8 +275,8 @@
       <title>Using the Prefix</title>
       <body>
         <p>
-          To use your bootstrapped prefix environment, you best start a
-          shell from the prefix, such that your path and other
+          To use your bootstrapped Prefix environment, you best start a
+          shell from the Prefix, such that your path and other
           environment variables are set correctly.  To facilitate in
           this, a small helper script can be created by the bootstrap
           script.
@@ -287,8 +289,8 @@
           After running this, a script <c>startprefix</c> will be
           present in <c>$EPREFIX</c>.  You can freely move the script to
           e.g. your homedir for convenience.  Running the script will
-          drop you into a prefix shell, where for example <c>emerge</c>
-          is directly at your disposal.  Enjoy your prefix!
+          drop you into a Prefix shell, where for example <c>emerge</c>
+          is directly at your disposal.  Enjoy your Prefix!
         </p>
       </body>
     </section>



-- 
gentoo-commits@l.g.o mailing list