public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen (grobian)" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: bootstrap-macos.xml
Date: Wed, 09 Jan 2008 18:08:43 +0000	[thread overview]
Message-ID: <E1JCfM3-0007hE-8G@stork.gentoo.org> (raw)

grobian     08/01/09 18:08:43

  Modified:             bootstrap-macos.xml
  Log:
  Fix bug #204996, and adjust to new bootstrap image

Revision  Changes    Path
1.23                 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.23&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml?rev=1.23&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml?r1=1.22&r2=1.23

Index: bootstrap-macos.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- bootstrap-macos.xml	4 Dec 2007 19:41:20 -0000	1.22
+++ bootstrap-macos.xml	9 Jan 2008 18:08:42 -0000	1.23
@@ -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.22 2007/12/04 19:41:20 grobian Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-macos.xml,v 1.23 2008/01/09 18:08:42 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>
@@ -19,8 +19,8 @@
   <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
   <license/>
 
-  <version>1.4</version>
-  <date>2007-11-08</date>
+  <version>1.5</version>
+  <date>2008-01-09</date>
 
   <chapter>
     <title>Bootstrapping on OS X</title>
@@ -102,8 +102,8 @@
         </pre>
         <note>Mac OS X Leopard (10.5) users should <b>NOT</b> bootstrap
           python!  It fails to compile and is not necessary.</note>
-        <note>Please note that <c>wget</c>, <c>sed</c> and <c>python</c> are
-          installed in <path>$EPREFIX/tmp</path>!</note>
+        <note>Please note that <c>wget</c>, <c>sed</c>, <c>python</c>,
+          etc. are installed in <path>$EPREFIX/tmp</path>!</note>
         <p>
           The script will setup the <path>$EPREFIX</path>
           directory, download a portage tree snapshot, unpack it and
@@ -175,7 +175,7 @@
           needs.
         </p>
         <pre caption="emerge texinfo">
-$ <i>emerge --oneshot --nodeps texinfo</i>
+$ <i>emerge --oneshot --nodeps help2man texinfo</i>
         </pre>
         <p>
           Now we can finish installing the autotools:
@@ -196,11 +196,14 @@
           <c>tar</c> in our prefix.  These are the last packages that we
           temporarily installed to bootstrap our system.
         </p>
-        <pre caption="emerge python">
+        <pre caption="emerge remaining packages">
 $ <i>emerge --oneshot --nodeps python</i>
 $ <i>emerge --oneshot --nodeps findutils</i>
 $ <i>emerge --oneshot --nodeps tar</i>
+$ <i>emerge --oneshot gawk</i>
         </pre>
+        <note>Mac OS X Leopard (10.5) users should <b>also</b> emerge
+          python here.</note>
         <p>
           Before we continue to emerge all ebuilds from <c>system</c>,
           we first install <c>portage</c>.  We need to overwrite the
@@ -213,13 +216,6 @@
 $ <i>env FEATURES="-collision-protect" emerge --oneshot --nodeps portage</i>
         </pre>
         <p>
-          Next, we get GNU <c>awk</c>, as most ebuilds expect this
-          <c>awk</c> when they use it.
-        </p>
-        <pre caption="emerge gawk">
-$ <i>emerge --oneshot gawk</i>
-        </pre>
-        <p>
           Some, if not many, scripts and tools within a Gentoo system
           assume the availability of the <c>baselayout</c> package.  We
           make sure here we have it, for this reason.  In fact, it would
@@ -250,13 +246,6 @@
           failures due to dependencies.
         </p>
         <p>
-          Since we have some basic stuff now, we might want the benefit
-          of an updated tree.  To use it, emerge <c>subversion</c>:
-        </p>
-        <pre caption="emerge subversion">
-$ <i>emerge subversion</i>
-        </pre>
-        <p>
           We can now update the tree.  Since snapshots now are actually
           (anonymous) SVN checkouts of the tree, we can immediately use
           SVN commands on the tree instead of checking a tree out first.
@@ -299,7 +288,7 @@
           have <c>-march=prescott</c> here to avoid compilation errors
           due to SSE instructions not being enabled.  PPC users can use
           their CPU's alias to enable CPU specific tuning, e.g.
-          <c>-mcpu=G5 -mtune=G5</c>.
+          <c>-mcpu=G5 -mtune=G5 -faltivec</c>.
         </note>
         <p>
           Since we're about to rebuild our system for the last time, we
@@ -310,14 +299,14 @@
         <pre caption="Unsetting LDFLAGS and CPPFLAGS variables">
 $ <i>unset LDFLAGS</i>
 $ <i>unset CPPFLAGS</i>
-$ <i>emerge -e system world</i>
+$ <i>emerge -e system</i>
         </pre>
         <note>
           tcsh users can use <c>unsetenv LDFLAGS</c> and alike for
           <c>CPPFLAGS</c>.
         </note>
         <p>
-          After <c>world</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.
         </p>



-- 
gentoo-commits@lists.gentoo.org mailing list



             reply	other threads:[~2008-01-09 18:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 18:08 Fabian Groffen (grobian) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-30 18:09 [gentoo-commits] gentoo commit in xml/htdocs/proj/en/gentoo-alt/prefix: bootstrap-macos.xml Fabian Groffen (grobian)
2012-04-05 17:35 Jeremy Olexa (darkside)
2012-03-24 13:15 Fabian Groffen (grobian)
2011-12-01 20:07 Fabian Groffen (grobian)
2011-11-29 17:21 Jeremy Olexa (darkside)
2011-04-10 12:44 Fabian Groffen (grobian)
2010-09-02 17:22 Fabian Groffen (grobian)
2010-07-02 14:24 Fabian Groffen (grobian)
2010-05-03 18:15 Fabian Groffen (grobian)
2010-05-02 15:49 Fabian Groffen (grobian)
2010-05-02 15:25 Fabian Groffen (grobian)
2010-05-02 14:53 Fabian Groffen (grobian)
2009-06-01 20:03 Fabian Groffen (grobian)
2009-04-16 20:01 Fabian Groffen (grobian)
2009-04-08 13:44 Jeremy Olexa (darkside)
2008-10-18  7:55 Fabian Groffen (grobian)
2008-05-05 15:14 Fabian Groffen (grobian)
2008-04-25 10:49 Fabian Groffen (grobian)
2008-04-13 19:27 Fabian Groffen (grobian)
2008-02-21 17:13 Fabian Groffen (grobian)
2008-02-21 16:46 Fabian Groffen (grobian)
2008-02-02 17:23 Fabian Groffen (grobian)
2008-01-09 18:23 Fabian Groffen (grobian)
2007-12-04 19:41 Fabian Groffen (grobian)
2007-11-15 18:26 Fabian Groffen (grobian)
2007-11-08 19:11 Fabian Groffen (grobian)
2007-11-08 19:01 Fabian Groffen (grobian)
2007-10-29  8:44 Fabian Groffen (grobian)
2007-10-24  8:34 Fabian Groffen (grobian)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1JCfM3-0007hE-8G@stork.gentoo.org \
    --to=grobian@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox