| 1 | <?xml version='1.0' encoding="UTF-8"?> |
1 | <?xml version='1.0' encoding="UTF-8"?> |
| 2 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
2 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 3 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.6 2004/07/26 19:44:43 dertobi123 Exp $ --> |
3 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.18 2005/01/25 11:48:14 neysx Exp $ --> |
| 4 | |
4 | |
| 5 | <guide link="/doc/en/gentoo-upgrading.xml"> |
5 | <guide link="/doc/en/gentoo-upgrading.xml"> |
| 6 | <title>Gentoo Upgrading Guide</title> |
6 | <title>Gentoo Upgrading Guide</title> |
| 7 | |
7 | |
| 8 | <author title="Author"> |
8 | <author title="Author"> |
| 9 | <mail link="g.guidi@sns.it">Gregorio Guidi</mail> |
9 | <mail link="greg_g@gentoo.org">Gregorio Guidi</mail> |
| 10 | </author> |
10 | </author> |
| 11 | |
11 | |
| 12 | <abstract> |
12 | <abstract> |
| 13 | This document explains how to react when a new Gentoo release is announced. |
13 | This document explains how new Gentoo releases affect existing installs. |
| 14 | </abstract> |
14 | </abstract> |
| 15 | |
15 | |
| 16 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
16 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 17 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
17 | <!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
| 18 | <license/> |
18 | <license/> |
| 19 | |
19 | |
| 20 | <version>1.3</version> |
20 | <version>2.8</version> |
| 21 | <date>July 26, 2004</date> |
21 | <date>2005-01-22</date> |
| 22 | |
22 | |
| 23 | <chapter> |
23 | <chapter> |
| 24 | <title>Gentoo and Upgrades</title> |
24 | <title>Gentoo and Upgrades</title> |
| 25 | <section> |
25 | <section> |
| 26 | <title>Philosophy</title> |
26 | <title>Philosophy</title> |
| 27 | <body> |
27 | <body> |
| 28 | |
28 | |
| 29 | <p> |
29 | <p> |
| 30 | Here in Gentoo land, the concept of upgrade is quite different with respect to |
30 | Here in Gentoo land, the concept of upgrading is quite different compared to |
| 31 | the rest of the linux world. Probably you already know that we never got in |
31 | the rest of the Linux world. You probably already know that we never got in |
| 32 | touch with the "classic" way to upgrade software in our distribution to the |
32 | touch with the "classic" way of upgrading software: waiting for a new release, |
| 33 | latest version: waiting for a new release, downloading it, burning, putting it |
33 | downloading it, burning, putting it in the cdrom drive and then following the |
| 34 | in the cdrom drive and then following the upgrade instructions. |
34 | upgrade instructions. |
| 35 | </p> |
|
|
| 36 | |
|
|
| 37 | <p> |
35 | </p> |
|
|
36 | |
|
|
37 | <p> |
| 38 | You know (you chose Gentoo, after all) that this process is extremely |
38 | You know (being a Gentoo user after all) that this process is extremely |
| 39 | frustrating for power users that want to live on the bleeding edge. Even power |
39 | frustrating for power users that want to live on the bleeding edge. Even power |
| 40 | users from other distributions must share the same feelings, given the |
40 | users from other distributions probably share the same feelings, given the |
| 41 | popularity and spread among them of tools like apt or apt-rpm, which make it |
41 | popularity and spread of tools like apt or apt-rpm which make it |
| 42 | possible to have quick and frequent updates. However, no distibution is more |
42 | possible to have quick and frequent updates. However, no distibution is more |
| 43 | suited than Gentoo to satisfy these kind of demanding users, because Gentoo was |
43 | suited than Gentoo to satisfy these kind of demanding users. From the beginning, |
| 44 | shaped from the beginning around the concept of fast, incremental updates. |
44 | Gentoo was designed around the concept of fast, incremental updates. |
| 45 | </p> |
|
|
| 46 | |
|
|
| 47 | <p> |
45 | </p> |
| 48 | Ideally, you install once and then do not bother anymore about releases: |
46 | |
| 49 | just follow the instructions in |
47 | <p> |
|
|
48 | Ideally, you install once and never bother with releases: just follow the |
|
|
49 | instructions in <uri |
| 50 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=2">Portage and |
50 | link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">A Portage |
| 51 | Software</uri> in the |
51 | Introduction</uri> in the <uri link="/doc/en/handbook/">Gentoo Handbook</uri> |
| 52 | <uri link="/doc/en/handbook/">Gentoo Handbook</uri> that explain how to keep |
52 | that explain how to keep your system up to date. While that's the way things |
| 53 | your system up to date. While that's the way things go usually, it can |
53 | usually go, sometimes changes are made to the core system which require updates |
| 54 | happen sometimes that developers push out, together with a new release, an |
54 | to be done manually. |
| 55 | update that touches the basics of the systems. We will consider these cases |
|
|
| 56 | below, when talking about profiles. |
|
|
| 57 | </p> |
55 | </p> |
| 58 | |
56 | |
| 59 | </body> |
57 | </body> |
| 60 | </section> |
58 | </section> |
| 61 | <section> |
59 | <section> |
| … | |
… | |
| 68 | There are various reasons: |
66 | There are various reasons: |
| 69 | </p> |
67 | </p> |
| 70 | |
68 | |
| 71 | <ul> |
69 | <ul> |
| 72 | <li> |
70 | <li> |
| 73 | A new release means enhanced and more feature-rich LiveCDs. |
71 | A new release means new LiveCDs with bugfixes and more features. |
| 74 | </li> |
72 | </li> |
| 75 | <li> |
73 | <li> |
| 76 | A new release provides an updated set of GRP packages, so that users that |
74 | A new release provides an updated set of GRP packages, so that users that |
| 77 | choose "the fast way" to install, stage3 + precompiled packages, end up |
75 | choose "the fast way" to install (stage3 + precompiled packages) end up |
| 78 | with a system that is not outdated. |
76 | with a system that is not outdated. |
| 79 | </li> |
77 | </li> |
| 80 | <li> |
78 | <li> |
| 81 | Finally, a new release may (not frequently) implement some features that |
79 | Finally, a new release may, from time to time, implement some features that |
| 82 | are incompatible with previous releases. |
80 | are incompatible with previous releases. |
| 83 | </li> |
81 | </li> |
| 84 | </ul> |
82 | </ul> |
| 85 | |
83 | |
| 86 | <p> |
84 | <p> |
| 87 | When a release provides new incompatible features, or provides a set of core |
85 | When a release includes new incompatible features, or provides a set of core |
| 88 | packages and settings that deeply modify the behavior of the system, or simply |
86 | packages and settings that deeply modify the behavior of the system, we say |
| 89 | when it makes tricky changes to some default parameters, we say that it |
|
|
| 90 | provides a new <e>profile</e>. |
87 | that it provides a new <e>profile</e>. |
| 91 | </p> |
88 | </p> |
| 92 | |
89 | |
| 93 | <p> |
90 | <p> |
| 94 | A <e>profile</e> is a set of configuration files, stored in a subdirectory of |
91 | A <e>profile</e> is a set of configuration files, stored in a subdirectory of |
| 95 | <path>/usr/portage/profiles/</path>, that describe things such as the ebuilds |
92 | <path>/usr/portage/profiles</path>, that describe things such as the ebuilds |
| 96 | that are considered <e>system</e> packages, the default USE flags, the default |
93 | that are considered <e>system</e> packages, the default USE flags, the default |
| 97 | mapping for virtual packages. |
94 | mapping for virtual packages, and the architecture on which the system is running. |
| 98 | </p> |
95 | </p> |
| 99 | |
96 | |
| 100 | <p> |
97 | <p> |
| 101 | The profile in use is determined by the symbolic link |
98 | The profile in use is determined by the symbolic link |
| 102 | <path>/etc/make.profile</path>, which points to the subdirectory of |
99 | <path>/etc/make.profile</path>, which points to a subdirectory of |
| 103 | <path>/usr/portage/profiles</path> which holds the profile files, for instance |
100 | <path>/usr/portage/profiles</path> which holds the profile files. For instance, |
| 104 | <path>/usr/portage/profiles/default-x86-2004.2</path> (old-style location) or |
101 | the x86 2004.2 profile can be found at <path>/usr/portage/profiles/default-x86-2004.2</path> |
| 105 | <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style |
102 | (old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style |
| 106 | location). With respect to new-style profile directories, note that also the |
103 | location - only for use with Portage 2.0.51 and later). With respect to new-style profile directories, note that the files in |
| 107 | files in parent directories are part of the profile (and are therefore shared |
104 | parent directories are part of the profile (and are therefore shared |
| 108 | by different profiles). |
105 | by different subprofiles). |
| 109 | </p> |
106 | </p> |
| 110 | |
107 | |
| 111 | <p> |
108 | <p> |
| 112 | Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> |
109 | Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> |
| 113 | as the current ones, but they are marked as deprecated. When that happens a |
110 | along with the current ones, but they are marked as deprecated. When that happens a |
| 114 | file named <path>deprecated</path> is put in the profile directory. The content |
111 | file named <path>deprecated</path> is put in the profile directory. The content |
| 115 | of this file is the name of the profile that should substitute it; portage uses |
112 | of this file is the name of the profile that should be "upgraded to"; portage uses |
| 116 | this information to automatically warn you about the new profile. |
113 | this information to automatically warn you when you should update to a new profile. |
| 117 | </p> |
|
|
| 118 | |
|
|
| 119 | <p> |
114 | </p> |
| 120 | There are various reasons that justify the creation of a new profile: the |
115 | |
|
|
116 | <p> |
|
|
117 | There are various reasons that a new profile may be created: the release of new |
| 121 | release of new versions of core packages (such as <c>baselayout</c>, <c>gcc</c> |
118 | versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or <c>glibc</c>) |
| 122 | or <c>glibc</c>) that are incompatible with previous versions, a change in the |
119 | that are incompatible with previous versions, a change in the default USE flags or |
| 123 | default USE flags, or in the virtual mappings, or maybe a change in system-wide |
120 | in the virtual mappings, or maybe a change in system-wide settings (such as defining |
| 124 | settings (such as defining udev to be the default manager for <path>/dev</path> |
121 | udev to be the default manager for <path>/dev</path> instead of devfs). |
| 125 | instead of devfs). |
|
|
| 126 | </p> |
122 | </p> |
| 127 | |
123 | |
| 128 | </body> |
124 | </body> |
| 129 | </section> |
125 | </section> |
| 130 | </chapter> |
126 | </chapter> |
| … | |
… | |
| 135 | <title>Releases without profile changes</title> |
131 | <title>Releases without profile changes</title> |
| 136 | <body> |
132 | <body> |
| 137 | |
133 | |
| 138 | <p> |
134 | <p> |
| 139 | If a new Gentoo release is announced that does not include a new profile (such |
135 | If a new Gentoo release is announced that does not include a new profile (such |
| 140 | as the 2004.1 release for x86), then you can safely pretend that it never |
136 | as the 2004.1 release for x86), then you can safely pretend that it never |
| 141 | happened. |
137 | happened :). |
| 142 | </p> |
|
|
| 143 | |
|
|
| 144 | <p> |
138 | </p> |
|
|
139 | |
|
|
140 | <p> |
| 145 | If you update your installed packages |
141 | If you update your installed packages |
| 146 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=2">as explained in |
142 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">as explained in |
| 147 | the Gentoo Handbook</uri>, then your system will be exactly the same as one |
143 | the Gentoo Handbook</uri>, then your system will be exactly the same as one |
| 148 | that has been installed using the new release. |
144 | that has been installed using the new release. |
| 149 | </p> |
145 | </p> |
| 150 | |
146 | |
| 151 | </body> |
147 | </body> |
| … | |
… | |
| 153 | <section> |
149 | <section> |
| 154 | <title>Releases with profile changes</title> |
150 | <title>Releases with profile changes</title> |
| 155 | <body> |
151 | <body> |
| 156 | |
152 | |
| 157 | <p> |
153 | <p> |
| 158 | If a release introduces a new profile, you have the choice to migrate to the |
154 | If a release introduces a new profile, you have the choice to migrate to the |
| 159 | new profile. |
155 | new profile. |
| 160 | </p> |
156 | </p> |
| 161 | |
157 | |
| 162 | <p> |
158 | <p> |
| 163 | Naturally, you are not forced to do so, you can continue to use the old profile |
159 | Naturally, you are not forced to do so, and you can continue to use the old profile |
| 164 | and just update your packages |
160 | and just update your packages |
| 165 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=2">as explained in |
161 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">as explained in |
| 166 | the Gentoo Handbook</uri> (or you may want to not update your system at all). |
162 | the Gentoo Handbook</uri>. |
| 167 | </p> |
|
|
| 168 | |
|
|
| 169 | <p> |
163 | </p> |
|
|
164 | |
|
|
165 | <p> |
| 170 | However, Gentoo strongly recommends a migration if your profile becomes |
166 | However, Gentoo strongly recommends updating your profile if it becomes deprecated. |
| 171 | deprecated and is no more supported by Gentoo developers, that is to say that |
167 | When this happens, it means that Gentoo developers no longer plan on supporting it. |
| 172 | your profile is not listed anymore in the table below. |
168 | Using the table below, you can quickly check to see what profiles are currently supported. |
| 173 | </p> |
169 | </p> |
| 174 | |
170 | |
| 175 | <p> |
171 | <p> |
| 176 | If you decide to migrate to the new profile, then you will have to manually |
172 | If you decide to migrate to the new profile, then you will have to manually |
| 177 | perform some actions. Those actions may vary a lot from release to release, it |
173 | perform the update. The way you update may vary significantly from release to release; it |
| 178 | depends on how deep the modifications introduced in the new profile are. |
174 | depends on how deep the modifications introduced in the new profile are. |
| 179 | </p> |
175 | </p> |
| 180 | |
176 | |
| 181 | <p> |
177 | <p> |
| 182 | In the simplest case you only have to change the <path>/etc/make.profile</path> |
178 | In the simplest case you only have to change the <path>/etc/make.profile</path> |
| 183 | link, in the worst case you may have to recompile your system from scratch |
179 | symlink, in the worst case you may have to recompile your system from scratch |
| 184 | while doing some voodoo stuff. In every case we will publish the instructions |
180 | while doing a neat voodoo dance. Migration is usually covered in the release |
| 185 | for the migration as part of the release. You can find these instructions also |
181 | notes (e.g. <uri |
| 186 | at the end of this guide. |
182 | link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3 |
|
|
183 | release notes</uri>). You can also find <uri |
|
|
184 | link="#instructions">instructions</uri> at the end of this guide. |
| 187 | </p> |
185 | </p> |
| 188 | |
186 | |
| 189 | </body> |
187 | </body> |
| 190 | </section> |
188 | </section> |
| 191 | <section> |
189 | <section> |
| … | |
… | |
| 201 | <th>Architecture</th> |
199 | <th>Architecture</th> |
| 202 | <th>Most recent profile</th> |
200 | <th>Most recent profile</th> |
| 203 | <th>Other supported profiles</th> |
201 | <th>Other supported profiles</th> |
| 204 | </tr> |
202 | </tr> |
| 205 | <tr> |
203 | <tr> |
|
|
204 | <th>alpha</th> |
|
|
205 | <ti>2004.3</ti> |
|
|
206 | <ti></ti> |
|
|
207 | </tr> |
|
|
208 | <tr> |
|
|
209 | <th>arm</th> |
|
|
210 | <ti>2004.3</ti> |
|
|
211 | <ti></ti> |
|
|
212 | </tr> |
|
|
213 | <tr> |
|
|
214 | <th>amd64</th> |
|
|
215 | <ti>2004.3</ti> |
|
|
216 | <ti>2004.2, 2004.0</ti> |
|
|
217 | </tr> |
|
|
218 | <tr> |
|
|
219 | <th>hppa</th> |
|
|
220 | <ti>2004.3</ti> |
|
|
221 | <ti>2004.2</ti> |
|
|
222 | </tr> |
|
|
223 | <tr> |
|
|
224 | <th>ia64</th> |
|
|
225 | <ti>2004.3</ti> |
|
|
226 | <ti></ti> |
|
|
227 | </tr> |
|
|
228 | <tr> |
|
|
229 | <th>ppc</th> |
|
|
230 | <ti>2004.3</ti> |
|
|
231 | <ti>2004.0</ti> |
|
|
232 | </tr> |
|
|
233 | <tr> |
|
|
234 | <th>mips</th> |
|
|
235 | <ti>2004.2</ti> |
|
|
236 | <ti></ti> |
|
|
237 | </tr> |
|
|
238 | <tr> |
|
|
239 | <th>s390</th> |
|
|
240 | <ti>2004.3</ti> |
|
|
241 | <ti></ti> |
|
|
242 | </tr> |
|
|
243 | <tr> |
|
|
244 | <th>sparc</th> |
|
|
245 | <ti>2004.3</ti> |
|
|
246 | <ti>2004.0</ti> |
|
|
247 | </tr> |
|
|
248 | <tr> |
| 206 | <th>x86</th> |
249 | <th>x86</th> |
| 207 | <ti>2004.2</ti> |
250 | <ti>2004.3</ti> |
| 208 | <ti>2004.0, 1.4</ti> |
|
|
| 209 | </tr> |
|
|
| 210 | <tr> |
|
|
| 211 | <th>hardened-x86</th> |
|
|
| 212 | <ti>2004.0</ti> |
251 | <ti>2004.2, 2004.0</ti> |
| 213 | <ti></ti> |
|
|
| 214 | </tr> |
|
|
| 215 | <tr> |
|
|
| 216 | <th>amd64</th> |
|
|
| 217 | <ti>2004.2</ti> |
|
|
| 218 | <ti>2004.0</ti> |
|
|
| 219 | </tr> |
|
|
| 220 | <tr> |
|
|
| 221 | <th>ppc</th> |
|
|
| 222 | <ti>2004.0</ti> |
|
|
| 223 | <ti></ti> |
|
|
| 224 | </tr> |
|
|
| 225 | <tr> |
|
|
| 226 | <th>sparc</th> |
|
|
| 227 | <ti>2004.0</ti> |
|
|
| 228 | <ti>1.4</ti> |
|
|
| 229 | </tr> |
|
|
| 230 | <tr> |
|
|
| 231 | <th>mips</th> |
|
|
| 232 | <ti>2004.1</ti> |
|
|
| 233 | <ti>1.4</ti> |
|
|
| 234 | </tr> |
|
|
| 235 | <tr> |
|
|
| 236 | <th>hppa</th> |
|
|
| 237 | <ti>2004.0</ti> |
|
|
| 238 | <ti></ti> |
|
|
| 239 | </tr> |
|
|
| 240 | <tr> |
|
|
| 241 | <th>arm</th> |
|
|
| 242 | <ti>2004.0</ti> |
|
|
| 243 | <ti></ti> |
|
|
| 244 | </tr> |
252 | </tr> |
| 245 | </table> |
253 | </table> |
| 246 | |
254 | |
| 247 | </body> |
255 | </body> |
| 248 | </section> |
256 | </section> |
| 249 | </chapter> |
257 | </chapter> |
| 250 | |
258 | |
| 251 | <chapter> |
259 | <chapter id="instructions"> |
| 252 | <title>Profile updating instructions</title> |
260 | <title>Profile updating instructions</title> |
| 253 | <section> |
261 | <section> |
| 254 | <title>Updating to 2004.2</title> |
262 | <title>Updating to 2004.3</title> |
| 255 | <body> |
263 | <body> |
| 256 | |
264 | |
|
|
265 | <p> |
|
|
266 | With the introduction of the 2004.3 profiles, users are not going to see huge |
|
|
267 | modifications of their systems (see below for details). However, Gentoo |
|
|
268 | developers decided to push out this new profile and to deprecate quite a few of |
|
|
269 | the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the |
|
|
270 | profiles that follow the new layout of the <path>/usr/portage/profiles</path> |
|
|
271 | directory, for instance |
|
|
272 | <path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by |
|
|
273 | Portage 2.0.51 or later). |
| 257 | <p> |
274 | </p> |
|
|
275 | |
|
|
276 | <p> |
| 258 | To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> link |
277 | To switch to the 2004.3 profile, point the <path>/etc/make.profile</path> |
| 259 | to the new location: |
278 | symlink to the new location: |
| 260 | </p> |
279 | </p> |
| 261 | |
280 | |
|
|
281 | <warn> |
|
|
282 | Don't forget to upgrade Portage <e>before</e> you change your profile!!! |
|
|
283 | </warn> |
|
|
284 | |
| 262 | <pre caption="Updating the /etc/make.profile link"> |
285 | <pre caption="Updating the /etc/make.profile symlink"> |
| 263 | <comment>substitute <arch> with your arch</comment> |
286 | <comment>substitute <arch> with your arch</comment> |
| 264 | # <i>rm /etc/make.profile</i> |
287 | # <i>rm /etc/make.profile</i> |
|
|
288 | # <i>ln -s ../usr/portage/profiles/default-linux/<arch>/2004.3 /etc/make.profile</i> |
|
|
289 | </pre> |
|
|
290 | |
|
|
291 | <p> |
|
|
292 | <b>All archs</b> - As said above, there are no big changes introduced in this |
|
|
293 | profile. However, it should be noted that <c>sys-apps/slocate</c> and |
|
|
294 | <c>net-misc/dhcpcd</c> are no longer considered system packages. This means |
|
|
295 | that if you run <c>emerge --depclean</c>, Portage will try to remove them from |
|
|
296 | your system. If you need any of those packages, add them to |
|
|
297 | <path>/var/lib/portage/world</path> after the profile switch, or manually |
|
|
298 | emerge them. |
|
|
299 | </p> |
|
|
300 | |
|
|
301 | <p> |
|
|
302 | <b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/devfs</c> |
|
|
303 | for newly installed machines. This has no effect on already installed machines, |
|
|
304 | though. |
|
|
305 | </p> |
|
|
306 | |
|
|
307 | </body> |
|
|
308 | </section> |
|
|
309 | <section> |
|
|
310 | <title>Updating to 2004.2</title> |
|
|
311 | <body> |
|
|
312 | |
|
|
313 | <p> |
|
|
314 | To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink |
|
|
315 | to the new location: |
|
|
316 | </p> |
|
|
317 | |
|
|
318 | <warn> |
|
|
319 | Don't forget to upgrade Portage <e>before</e> you change your profile!!! |
|
|
320 | </warn> |
|
|
321 | |
|
|
322 | <pre caption="Updating the /etc/make.profile symlink"> |
|
|
323 | <comment>substitute <arch> with your arch</comment> |
|
|
324 | # <i>rm /etc/make.profile</i> |
| 265 | # <i>ln -s ../usr/portage/profiles/default-<arch>-2004.2 /etc/make.profile</i> |
325 | # <i>ln -s ../usr/portage/profiles/default-linux/<arch>/2004.2 /etc/make.profile</i> |
| 266 | </pre> |
326 | </pre> |
| 267 | |
327 | |
| 268 | <p> |
328 | <p> |
| 269 | <b>x86</b> - This profile changes the default X11 implementation from |
329 | <b>x86</b> - This profile changes the default X11 implementation from |
| 270 | <c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches |
330 | <c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches |
| 271 | the <e>default</e> value, and is only relevant for those who have not installed |
331 | the <e>default</e> value, and is only relevant for those who have not installed |
| 272 | an X server yet. If you already have one installed, then it will not affect |
332 | an X server yet. If you already have one installed, then it will not affect |
| 273 | you at all, you are free to switch from one X server to the other exactly as |
333 | you at all; you are free to switch from one X server to the other exactly as |
| 274 | before. |
334 | before. |
| 275 | </p> |
335 | </p> |
| 276 | |
336 | |
| 277 | <p> |
337 | <p> |
| 278 | <b>amd64</b> - There are no fundamental changes from previous profiles, no |
338 | <b>amd64</b> - There are no fundamental changes from previous profiles, no |
| … | |
… | |
| 284 | <section> |
344 | <section> |
| 285 | <title>Updating to 2004.0</title> |
345 | <title>Updating to 2004.0</title> |
| 286 | <body> |
346 | <body> |
| 287 | |
347 | |
| 288 | <p> |
348 | <p> |
| 289 | To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> link |
349 | To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> symlink |
| 290 | to the new location: |
350 | to the new location: |
| 291 | </p> |
351 | </p> |
| 292 | |
352 | |
| 293 | <pre caption="Updating the /etc/make.profile link"> |
353 | <pre caption="Updating the /etc/make.profile symlink"> |
| 294 | <comment>substitute <arch> with your arch</comment> |
354 | <comment>substitute <arch> with your arch</comment> |
| 295 | # <i>rm /etc/make.profile</i> |
355 | # <i>rm /etc/make.profile</i> |
| 296 | # <i>ln -s ../usr/portage/profiles/default-<arch>-2004.0 /etc/make.profile</i> |
356 | # <i>ln -s ../usr/portage/profiles/default-<arch>-2004.0 /etc/make.profile</i> |
| 297 | </pre> |
357 | </pre> |
| 298 | |
358 | |
| … | |
… | |
| 315 | </body> |
375 | </body> |
| 316 | </section> |
376 | </section> |
| 317 | </chapter> |
377 | </chapter> |
| 318 | |
378 | |
| 319 | </guide> |
379 | </guide> |
| 320 | |
|
|
Parent Directory
| 
Revision Log
| 
Patch