1 |
grobian 08/01/09 18:22:36 |
2 |
|
3 |
Modified: bootstrap-freebsd.xml |
4 |
Log: |
5 |
Adjust to latest bootstrap image |
6 |
|
7 |
Revision Changes Path |
8 |
1.7 xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml?rev=1.7&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml?rev=1.7&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml?r1=1.6&r2=1.7 |
13 |
|
14 |
Index: bootstrap-freebsd.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml,v |
17 |
retrieving revision 1.6 |
18 |
retrieving revision 1.7 |
19 |
diff -u -r1.6 -r1.7 |
20 |
--- bootstrap-freebsd.xml 29 Oct 2007 09:58:01 -0000 1.6 |
21 |
+++ bootstrap-freebsd.xml 9 Jan 2008 18:22:35 -0000 1.7 |
22 |
@@ -1,6 +1,6 @@ |
23 |
<?xml version="1.0" encoding="UTF-8"?> |
24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml,v 1.6 2007/10/29 09:58:01 grobian Exp $ --> |
26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml,v 1.7 2008/01/09 18:22:35 grobian Exp $ --> |
27 |
|
28 |
<guide link="/proj/en/gentoo-alt/prefix/bootstrap-freebsd.xml" lang="en"> |
29 |
<title>Gentoo Prefixed Portage Bootstrap Process for FreeBSD</title> |
30 |
@@ -19,8 +19,8 @@ |
31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
32 |
<license/> |
33 |
|
34 |
- <version>1.0</version> |
35 |
- <date>2007-10-29</date> |
36 |
+ <version>1.1</version> |
37 |
+ <date>2008-01-09</date> |
38 |
|
39 |
<chapter> |
40 |
<title>Bootstrapping on FreeBSD</title> |
41 |
@@ -162,7 +162,7 @@ |
42 |
assume the availability of the <c>baselayout</c> package for |
43 |
all communication using the Gentoo colour scheme. |
44 |
</p> |
45 |
- <pre caption="emerge bash"> |
46 |
+ <pre caption="emerge autotools"> |
47 |
$ <i>emerge --oneshot m4</i> |
48 |
$ <i>emerge --oneshot --nodeps baselayout-prefix</i> |
49 |
$ <i>emerge --oneshot flex</i> |
50 |
@@ -186,7 +186,7 @@ |
51 |
needs. |
52 |
</p> |
53 |
<pre caption="emerge texinfo"> |
54 |
-$ <i>emerge --oneshot --nodeps texinfo</i> |
55 |
+$ <i>emerge --oneshot --nodeps help2man texinfo</i> |
56 |
</pre> |
57 |
<p> |
58 |
Now we can finish installing the autotools: |
59 |
@@ -213,6 +213,7 @@ |
60 |
$ <i>emerge --oneshot --nodeps findutils</i> |
61 |
$ <i>emerge --oneshot --nodeps tar</i> |
62 |
$ <i>emerge --oneshot --nodeps patch</i> |
63 |
+$ <i>emerge --oneshot gawk</i> |
64 |
</pre> |
65 |
<p> |
66 |
Before we continue to emerge all ebuilds from <c>system</c>, |
67 |
@@ -226,13 +227,6 @@ |
68 |
$ <i>env FEATURES="-collision-protect" emerge --oneshot --nodeps portage</i> |
69 |
</pre> |
70 |
<p> |
71 |
- Next, we get GNU <c>awk</c>, as most ebuilds expect this |
72 |
- <c>awk</c> when they use it. |
73 |
- </p> |
74 |
- <pre caption="emerge gawk"> |
75 |
-$ <i>emerge --oneshot gawk</i> |
76 |
- </pre> |
77 |
- <p> |
78 |
Now we're about to start the big work, we remove the temporary |
79 |
directory and its use as we got it all in our prefix now. |
80 |
</p> |
81 |
@@ -254,13 +248,6 @@ |
82 |
failures due to dependencies. |
83 |
</p> |
84 |
<p> |
85 |
- Since we have some basic stuff now, we might want the benefit |
86 |
- of an updated tree. To use it, emerge <c>subversion</c>: |
87 |
- </p> |
88 |
- <pre caption="emerge subversion"> |
89 |
-$ <i>emerge subversion</i> |
90 |
- </pre> |
91 |
- <p> |
92 |
We can now update the tree. Since snapshots now are actually |
93 |
(anonymous) SVN checkouts of the tree, we can immediately use |
94 |
SVN commands on the tree instead of checking a tree out first. |
95 |
@@ -274,7 +261,7 @@ |
96 |
</pre> |
97 |
<p> |
98 |
To really do this properly, after emerging <c>system</c>, one |
99 |
- should re-emerge <c>world</c>, because now all packages can |
100 |
+ should re-emerge <c>system</c>, because now all packages can |
101 |
be compiled with all tools from the prefix, instead of based |
102 |
on tools in the system root. Before you do though, this is |
103 |
the good time to set your general <c>USE</c>-flags, such as |
104 |
@@ -292,20 +279,18 @@ |
105 |
<p> |
106 |
Since we're about to rebuild our system for the last time, we |
107 |
can unset all hacks we made to help the bootstrap process. |
108 |
- This time we emerge <c>world</c> to include the packages |
109 |
- necessary for <c>subversion</c>. |
110 |
</p> |
111 |
<pre caption="Unsetting LDFLAGS and CPPFLAGS variables"> |
112 |
$ <i>unset LDFLAGS</i> |
113 |
$ <i>unset CPPFLAGS</i> |
114 |
-$ <i>emerge -e system world</i> |
115 |
+$ <i>emerge -e system</i> |
116 |
</pre> |
117 |
<note> |
118 |
tcsh users can use <c>unsetenv LDFLAGS</c> and alike for |
119 |
<c>CPPFLAGS</c>. |
120 |
</note> |
121 |
<p> |
122 |
- After <c>world</c> has emerged successfully, your prefix will |
123 |
+ After <c>system</c> has emerged successfully, your prefix will |
124 |
be set up properly, and you can emerge the whichever tools you |
125 |
choose from the prefix tree. |
126 |
</p> |
127 |
|
128 |
|
129 |
|
130 |
-- |
131 |
gentoo-commits@l.g.o mailing list |