/[gentoo]/xml/htdocs/doc/en/gentoo-upgrading.xml
Gentoo

Diff of /xml/htdocs/doc/en/gentoo-upgrading.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.2 Revision 1.25
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.2 2004/05/15 01:02:37 neysx Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.25 2005/09/20 18:24:14 swift 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>
13This document explains how to react when a new Gentoo release is announced. 13This 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.5 -->
18<license/> 18<license/>
19 19
20<version>1.1</version> 20<version>2.13</version>
21<date>May 12, 2004</date> 21<date>2005-08-12</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>
30Here in Gentoo land, the concept of upgrade is quite different with respect to 30Here in Gentoo land, the concept of upgrading is quite different compared to
31the rest of the linux world. Probably you already know that we never got in 31the rest of the Linux world. You probably already know that we never got in
32touch with the "classic" way to upgrade software in our distribution to the 32touch with the "classic" way of upgrading software: waiting for a new release,
33latest version: waiting for a new release, downloading it, burning, putting it 33downloading it, burning, putting it in the cdrom drive and then following the
34in the cdrom drive and then following the upgrade instructions. 34upgrade instructions.
35</p>
36
37<p> 35</p>
36
37<p>
38You know (you chose Gentoo, after all) that this process is extremely 38You know (being a Gentoo user after all) that this process is extremely
39frustrating for power users that want to live on the bleeding edge. Even power 39frustrating for power users that want to live on the bleeding edge. Even power
40users from other distributions must share the same feelings, given the 40users from other distributions probably share the same feelings, given the
41popularity and spread among them of tools like apt or apt-rpm, which make it 41popularity and spread of tools like apt or apt-rpm which make it
42possible to have quick and frequent updates. However, no distibution is more 42possible to have quick and frequent updates. However, no distribution is more
43suited than Gentoo to satisfy these kind of demanding users, because Gentoo was 43suited than Gentoo to satisfy these kind of demanding users. From the
44shaped from the beginning around the concept of fast, incremental updates. 44beginning, Gentoo was designed around the concept of fast, incremental
45</p> 45updates.
46
47<p> 46</p>
48Ideally, you install once and then do not bother anymore about releases: 47
49just follow the instructions in 48<p>
49Ideally, you install once and never bother with releases: just follow the
50instructions in <uri
50<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">Portage and 51link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage
51Software</uri> in the 52Introduction</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 53that explain how to keep your system up to date. While that's the way things
53your system up to date. While that's the way things go usually, it can 54usually go, sometimes changes are made to the core system which require updates
54happen sometimes that developers push out, together with a new release, an 55to be done manually.
55update that touches the basics of the systems. We will consider these cases
56below, when talking about profiles.
57</p> 56</p>
58 57
59</body> 58</body>
60</section> 59</section>
61<section> 60<section>
68There are various reasons: 67There are various reasons:
69</p> 68</p>
70 69
71<ul> 70<ul>
72 <li> 71 <li>
73 A new release means enhanced and more feature-rich LiveCDs. 72 A new release means new Installation CDs with bugfixes and more features.
74 </li> 73 </li>
75 <li> 74 <li>
76 A new release provides an updated set of GRP packages, so that users that 75 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 76 choose "the fast way" to install (stage3 + precompiled packages) end up
78 with a system that is not outdated. 77 with a system that is not outdated.
79 </li> 78 </li>
80 <li> 79 <li>
81 Finally, a new release may (not frequently) implement some features that 80 Finally, a new release may, from time to time, implement some features that
82 are incompatible with previous releases. 81 are incompatible with previous releases.
83 </li> 82 </li>
84</ul> 83</ul>
85 84
86<p> 85<p>
87When a release provides new incompatible features, or provides a set of core 86When a release includes new incompatible features, or provides a set of core
88packages and settings that deeply modify the behavior of the system, or simply 87packages and settings that deeply modify the behavior of the system, we say
89when it makes tricky changes to some default parameters, we say that it
90provides a new <e>profile</e>. 88that it provides a new <e>profile</e>.
91</p> 89</p>
92 90
93<p> 91<p>
94A <e>profile</e> is a set of configuration files, stored in a subdirectory of 92A <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 93<path>/usr/portage/profiles</path>, that describe things such as the ebuilds
96that are considered <e>system</e> packages, the default USE flags, the default 94that are considered <e>system</e> packages, the default USE flags, the default
97mapping for virtual packages. 95mapping for virtual packages, and the architecture on which the system is running.
98</p> 96</p>
99 97
100<p> 98<p>
101The profile in use is determined by the symbolic link 99The profile in use is determined by the symbolic link
102<path>/etc/make.profile</path>, which points to the subdirectory of 100<path>/etc/make.profile</path>, which points to a subdirectory of
103<path>/usr/portage/profiles</path> which holds the profile files, for instance <path>/usr/portage/profiles/default-x86-2004.0</path>. 101<path>/usr/portage/profiles</path> which holds the profile files. For
102instance, the default x86 2005.1 profile can be found
103at <path>/usr/portage/profiles/default-linux/x86/2005.1</path>.
104The files in the parent directories are part of the profile as well (and
105are therefore shared by different subprofiles). This is why we call these
106<e>cascaded profiles</e>.
104</p> 107</p>
105 108
106<p> 109<p>
107Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> 110Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path>
108as the current ones, but they are marked as deprecated. When that happens a 111along with the current ones, but they are marked as deprecated. When that
109file named <path>deprecated</path> is put in the profile directory. The content 112happens a file named <path>deprecated</path> is put in the profile directory.
110of this file is the name of the profile that should substitute it; portage uses 113The content of this file is the name of the profile that should be "upgraded
111this information to automatically warn you about the new profile. 114to"; portage uses this information to automatically warn you when you should
112</p> 115update to a new profile.
113
114<p> 116</p>
115There are various reasons that justify the creation of a new profile: the 117
118<p>
119There are various reasons that a new profile may be created: the release of
116release of new versions of core packages (such as <c>baselayout</c>, <c>gcc</c> 120new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or
117or <c>glibc</c>) that are incompatible with previous versions, a change in the 121<c>glibc</c>) that are incompatible with previous versions, a change in
118default USE flags, or in the virtual mappings, or maybe a change in system-wide 122the default USE flags or in the virtual mappings, or maybe a change in
119settings (such as defining udev to be the default manager for <path>/dev</path> 123system-wide settings.
120instead of devfs).
121</p> 124</p>
122 125
123</body> 126</body>
124</section> 127</section>
125</chapter> 128</chapter>
129<section> 132<section>
130<title>Releases without profile changes</title> 133<title>Releases without profile changes</title>
131<body> 134<body>
132 135
133<p> 136<p>
134If a new Gentoo release is announced that does not include a new profile (such 137If a new Gentoo release is announced that does not include a new profile
135as the 2004.1 release for x86), then you can safely pretend that it never 138then you can safely pretend that it never happened :).
136happened.
137</p>
138
139<p> 139</p>
140
141<p>
140If you update your installed packages 142If you update your installed packages
141<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">as explained in 143<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
142the Gentoo Handbook</uri>, then your system will be exactly the same as one 144the Gentoo Handbook</uri>, then your system will be exactly the same as one
143that has been installed using the new release. 145that has been installed using the new release.
144</p> 146</p>
145 147
146</body> 148</body>
148<section> 150<section>
149<title>Releases with profile changes</title> 151<title>Releases with profile changes</title>
150<body> 152<body>
151 153
152<p> 154<p>
153If a release introduces a new profile, you have the choice to migrate to the 155If a release (such as 2005.1 for x86) introduces a new profile, you have the
154new profile. 156choice to migrate to the new profile.
155</p>
156
157<p> 157</p>
158
159<p>
158Naturally, you are not forced to do so, you can continue to use the old profile 160Naturally, you are not forced to do so, and you can continue to use the old
159and just update your packages 161profile and just update your packages
160<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">as explained in 162<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained
161the Gentoo Handbook</uri> (or you may want to not update your system at all). 163in the Gentoo Handbook</uri>.
162</p>
163
164<p> 164</p>
165
166<p>
165However, Gentoo strongly recommends a migration if your profile becomes 167However, Gentoo strongly recommends updating your profile if it becomes
166deprecated and is no more supported by Gentoo developers, that is to say that 168deprecated. When this happens, it means that Gentoo developers no longer
167your profile is not listed anymore in the table below. 169plan on supporting it. Using the table below, you can quickly check to
170see what profiles are currently supported.
168</p> 171</p>
169 172
170<p> 173<p>
171If you decide to migrate to the new profile, then you will have to manually 174If you decide to migrate to the new profile, then you will have to manually
172perform some actions. Those actions may vary a lot from release to release, it 175perform the update. The way you update may vary significantly from release
173depends on how deep the modifications introduced in the new profile are. 176to release; it depends on how deep the modifications introduced in the new
177profile are.
174</p> 178</p>
175 179
176<p> 180<p>
177In the simplest case you only have to change the <path>/etc/make.profile</path> 181In the simplest case you only have to change the <path>/etc/make.profile</path>
178link, in the worst case you may have to recompile your system from scratch 182symlink, in the worst case you may have to recompile your system from scratch
179while doing some voodoo stuff. In every case we will publish the instructions 183while doing a neat voodoo dance. Migration is usually covered in the release
180for the migration as part of the release. You can find these instructions also 184notes. You can also find <uri link="#instructions">instructions</uri> at the
181at the end of this guide. 185end of this guide.
182</p> 186</p>
183 187
184</body> 188</body>
185</section> 189</section>
186<section> 190<section>
192</p> 196</p>
193 197
194<table> 198<table>
195<tr> 199<tr>
196 <th>Architecture</th> 200 <th>Architecture</th>
197 <th>Most recent profile</th> 201 <th>Most recent profiles</th>
198 <th>Other supported profiles</th> 202 <th>Other supported profiles</th>
199</tr> 203</tr>
200<tr> 204<tr>
205 <th>alpha</th>
206 <ti>2005.0, 2005.0/2.4</ti>
207 <ti></ti>
208</tr>
209<tr>
210 <th>arm</th>
211 <ti>2004.3</ti>
212 <ti></ti>
213</tr>
214<tr>
215 <th>amd64</th>
216 <ti>2005.1, 2005.1/no-multilib</ti>
217 <ti>2005.0, 2005.0/no-multilib, 2004.3</ti>
218</tr>
219<tr>
220 <th>hppa</th>
221 <ti>2005.0, 2005.0/2.4</ti>
222 <ti>2004.3, 2004.2</ti>
223</tr>
224<tr>
225 <th>ia64</th>
226 <ti>2005.0</ti>
227 <ti>2004.3</ti>
228</tr>
229<tr>
230 <th>ppc</th>
231 <ti>2005.1</ti>
232 <ti>2005.0, 2004.3, 2004.0</ti>
233</tr>
234<tr>
235 <th>mips</th>
236 <ti>2005.0</ti>
237 <ti>2004.2</ti>
238</tr>
239<tr>
240 <th>s390</th>
241 <ti>2004.3</ti>
242 <ti></ti>
243</tr>
244<tr>
245 <th>sparc</th>
246 <ti>2005.1</ti>
247 <ti>2005.0</ti>
248</tr>
249<tr>
201 <th>x86</th> 250 <th>x86</th>
202 <ti>2004.0</ti> 251 <ti>2005.1, 2005.1/2.4</ti>
203 <ti>1.4</ti> 252 <ti>2005.0, 2005.0/2.4</ti>
204</tr>
205<tr>
206 <th>hardened-x86</th>
207 <ti>2004.0</ti>
208 <ti></ti>
209</tr>
210<tr>
211 <th>amd64</th>
212 <ti>2004.0</ti>
213 <ti></ti>
214</tr>
215<tr>
216 <th>ppc</th>
217 <ti>2004.0</ti>
218 <ti>1.4</ti>
219</tr>
220<tr>
221 <th>sparc</th>
222 <ti>2004.0</ti>
223 <ti>1.4</ti>
224</tr>
225<tr>
226 <th>mips</th>
227 <ti>2004.0</ti>
228 <ti>1.4</ti>
229</tr>
230<tr>
231 <th>hppa</th>
232 <ti>2004.0</ti>
233 <ti></ti>
234</tr> 253</tr>
235</table> 254</table>
236 255
237</body> 256</body>
238</section> 257</section>
239</chapter> 258</chapter>
240 259
241<chapter> 260<chapter id="instructions">
242<title>Profile updating instructions</title> 261<title>Profile updating instructions</title>
243<section> 262<section>
244<title>Updating from 1.4 to 2004.0 (all archs)</title> 263<title>Updating to 2005.1</title>
245<body> 264<body>
246 265
247<p>
248There are no fundamental changes between 1.4 and 2004.0 profiles. Just point
249the <path>/etc/make.profile</path> link to the new location:
250</p> 266<p>
267To switch to the 2005.1 profile, point the <path>/etc/make.profile</path>
268symlink to the new location. Make sure your Portage is updated before you
269change your profile.
270</p>
251 271
252<pre caption="Updating the /etc/make.profile link"> 272<pre caption="Changing to a 2005.1 profile">
253# <i>rm /etc/make.profile</i> 273# <i>rm /etc/make.profile</i>
254# <i>ln -s ../usr/portage/profiles/default-x86-2004.0 /etc/make.profile</i> 274# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
255</pre> 275</pre>
276
277<p>
278<b>All archs</b> - There are no fundamental changes in this profile. No
279specific action needs to be performed.
280</p>
281
282<p>
283<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged
284and a number of subprofiles for specific subarchitectures were created. Make
285sure you choose the correct subprofile for your system when migrating to a
2862005.1 profile.
287</p>
288
289</body>
290</section>
291<section>
292<title>Updating to 2005.0</title>
293<body>
294
295<p>
296With the introduction of 2005.0, several architectures have decided to define
297additional profiles. Make sure you read the description of said profiles before
298you decide to migrate to one of them. Most architectures now also default to the
2992.6 kernel tree where 2.4 was chosen previously.
300</p>
301
302<p>
303Some architectures require a bit more actions to be completed in order to
304convert from one profile to another. If that is the case, the step-by-step
305guides are linked from the table.
306</p>
307
308<table>
309<tr>
310 <th>Profile</th>
311 <th>Description</th>
312 <th>Specific Upgrade Guide</th>
313</tr>
314<tr>
315 <ti>default-linux/alpha/2005.0</ti>
316 <ti>Default Alpha 2005.0 profile for 2.6 kernels</ti>
317 <ti></ti>
318</tr>
319<tr>
320 <ti>default-linux/alpha/2005.0/2.4</ti>
321 <ti>Alpha 2005.0 profile for 2.4 kernels</ti>
322 <ti></ti>
323</tr>
324<tr>
325 <ti>default-linux/amd64/2005.0</ti>
326 <ti>Default AMD64 2005.0 profile for 2.6 kernels</ti>
327 <ti>
328 <uri
329 link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1#doc_chap1">Upgrading to
330 2005.0</uri>
331 </ti>
332</tr>
333<tr>
334 <ti>default-linux/amd64/2005.0/no-multilib</ti>
335 <ti>AMD64 2005.0 profile for multilib-disabled system installations</ti>
336 <ti>
337 <uri link="/proj/en/base/amd64/howtos/index.xml?part=1&amp;chap=1#doc_chap5">Upgrading to
338 2005.0</uri>
339 </ti>
340</tr>
341<tr>
342 <ti>default-linux/arm/2005.0</ti>
343 <ti>Default ARM 2005.0 profile for 2.6 kernels</ti>
344 <ti></ti>
345</tr>
346<tr>
347 <ti>default-linux/hppa/2005.0</ti>
348 <ti>Default HPPA 2005.0 profile for 2.6 kernels</ti>
349 <ti></ti>
350</tr>
351<tr>
352 <ti>default-linux/hppa/2005.0/2.4</ti>
353 <ti>HPPA 2005.0 profile for 2.4 kernels</ti>
354 <ti></ti>
355</tr>
356<tr>
357 <ti>default-linux/mips/2005.0</ti>
358 <ti>Default MIPS 2005.0 profile</ti>
359 <ti></ti>
360</tr>
361<tr>
362 <ti>default-linux/mips/cobalt/2005.0</ti>
363 <ti>Cobalt specific MIPS 2005.0 profile</ti>
364 <ti></ti>
365</tr>
366<tr>
367 <ti>default-linux/mips/mips64/n32/2005.0</ti>
368 <ti>2005.0 profile for n32-supporting MIPS platforms</ti>
369 <ti></ti>
370</tr>
371<tr>
372 <ti>default-linux/mips/mips64/ip28/2005.0</ti>
373 <ti>Indigo2 Impact specific 64-bit 2005.0 profile</ti>
374 <ti></ti>
375</tr>
376<tr>
377 <ti>default-linux/mips/mips64/2005.0</ti>
378 <ti>64-bit MIPS 2005.0 profile</ti>
379 <ti></ti>
380</tr>
381<tr>
382 <ti>default-linux/ppc/2005.0</ti>
383 <ti>Default PPC 2005.0 profile for 2.6 kernels</ti>
384 <ti></ti>
385</tr>
386<tr>
387 <ti>default-linux/ppc64/2005.0</ti>
388 <ti>Default PPC64 2005.0 profile for 2.6 kernels</ti>
389 <ti></ti>
390</tr>
391<tr>
392 <ti>default-linux/s390/2005.0</ti>
393 <ti>Default S390 2005.0 profile</ti>
394 <ti></ti>
395</tr>
396<tr>
397 <ti>default-linux/sparc/sparc32/2005.0</ti>
398 <ti>Default Sparc 32-bit 2005.0 profile</ti>
399 <ti></ti>
400</tr>
401<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
402 No subprofiles for sparc
403<tr>
404 <ti>default-linux/sparc/sparc32/2005.0/2.6</ti>
405 <ti>Sparc 32-bit 2005.0 profile for 2.6 kernels</ti>
406 <ti></ti>
407</tr>
408-->
409<tr>
410 <ti>default-linux/sparc/sparc64/2005.0</ti>
411 <ti>Default Sparc 64-bit 2005.0 profile</ti>
412 <ti></ti>
413</tr>
414<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
415 No subprofiles for sparc
416<tr>
417 <ti>default-linux/sparc/sparc64/2005.0/2.6</ti>
418 <ti>Sparc 64-bit 2005.0 profile for 2.6 kernels</ti>
419 <ti></ti>
420</tr>
421-->
422<tr>
423 <ti>default-linux/x86/2005.0</ti>
424 <ti>Default x86 2005.0 profile for 2.6 kernels</ti>
425 <ti></ti>
426</tr>
427<tr>
428 <ti>default-linux/x86/2005.0/2.4</ti>
429 <ti>x86 2005.0 profile for 2.4 kernels</ti>
430 <ti></ti>
431</tr>
432</table>
433
434<p>
435To switch to the selected profile, point the <path>/etc/make.profile</path>
436symlink to the new location. Make sure your Portage is updated before you change
437your profile!
438</p>
439
440<pre caption="Changing to a 2005.0 profile">
441# <i>rm /etc/make.profile</i>
442# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
443</pre>
444
445<p>
446If you are running a Linux 2.4-based system but want to migrate to a 2.6-based
447kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo
448Linux 2.6 Migration Guide</uri>.
449</p>
450
451</body>
452</section>
453<section>
454<title>Updating to 2004.3</title>
455<body>
456
457<p>
458With the introduction of the 2004.3 profiles, users are not going to see huge
459modifications of their systems (see below for details). However, Gentoo
460developers decided to push out this new profile and to deprecate quite a few of
461the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the
462profiles that follow the new layout of the <path>/usr/portage/profiles</path>
463directory, for instance
464<path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
465Portage 2.0.51 or later).
466</p>
467
468<p>
469To switch to the 2004.3 profile, point the <path>/etc/make.profile</path>
470symlink to the new location:
471</p>
472
473<warn>
474Don't forget to upgrade Portage <e>before</e> you change your profile!!!
475</warn>
476
477<pre caption="Updating the /etc/make.profile symlink">
478<comment>substitute &lt;arch&gt; with your arch</comment>
479# <i>rm /etc/make.profile</i>
480# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i>
481</pre>
482
483<p>
484<b>All archs</b> - As said above, there are no big changes introduced in this
485profile. However, it should be noted that <c>sys-apps/slocate</c> and
486<c>net-misc/dhcpcd</c> are no longer considered system packages. This means
487that if you run <c>emerge --depclean</c>, Portage will try to remove them from
488your system. If you need any of those packages, add them to
489<path>/var/lib/portage/world</path> after the profile switch, or manually
490emerge them.
491</p>
492
493<p>
494<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of
495<c>sys-fs/devfs</c> for newly installed machines. This has no
496effect on already installed machines, though.
497</p>
498
499</body>
500</section>
501<section>
502<title>Updating Portage to Support Cascading Profiles</title>
503<body>
504
505<p>
506Although this section does not seem to integrate well in this upgrading guide,
507it is quite important. Any profile listed above this section requires a Portage
508version that supports cascading profiles. However, some obsoleted profiles don't
509allow the user to upgrade Portage or the user is using a profile that isn't
510available anymore - any attempt to upgrade Portage will result in a failure.
511</p>
512
513<p>
514To work around this problem, users can set a temporary symbolic link to the
515<e>obsolete</e> profile, allowing them to upgrade their Portage after which
516they can continue with the upgrade procedure set forth in this guide:
517</p>
518
519<pre caption="Updating Portage through the obsolete profile">
520# <i>rm /etc/make.profile</i>
521# <i>cd /etc</i>
522# <i>ln -sf ../usr/portage/profiles/obsolete make.profile</i>
523# <i>emerge -n '>=sys-apps/portage-2.0.51'</i>
524</pre>
525
526</body>
527</section>
528<section>
529<title>Updating to 2004.2</title>
530<body>
531
532<p>
533To switch to the 2004.2 profile, point the <path>/etc/make.profile</path>
534symlink to the new location:
535</p>
536
537<warn>
538Don't forget to upgrade Portage <e>before</e> you change your profile!!!
539</warn>
540
541<pre caption="Updating the /etc/make.profile symlink">
542<comment>substitute &lt;arch&gt; with your arch</comment>
543# <i>rm /etc/make.profile</i>
544# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i>
545</pre>
546
547<p>
548<b>x86</b> - This profile changes the default X11 implementation from
549<c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches
550the <e>default</e> value, and is only relevant for those who have not installed
551an X server yet. If you already have one installed, then it will not affect
552you at all; you are free to switch from one X server to the other exactly as
553before.
554</p>
555
556<p>
557<b>amd64</b> - There are no fundamental changes from previous profiles, no
558specific action needs to be performed.
559</p>
560
561</body>
562</section>
563<section>
564<title>Updating to 2004.0</title>
565<body>
566
567<p>
568To switch to the 2004.0 profile, point the <path>/etc/make.profile</path>
569symlink to the new location:
570</p>
571
572<pre caption="Updating the /etc/make.profile symlink">
573<comment>substitute &lt;arch&gt; with your arch</comment>
574# <i>rm /etc/make.profile</i>
575# <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/make.profile</i>
576</pre>
577
578<p>
579<b>All archs</b> - There are no fundamental changes from previous profiles, no
580specific action needs to be performed.
581</p>
256 582
257</body> 583</body>
258</section> 584</section>
259<section> 585<section>
260<title>Updating from profiles older than 1.4 to 1.4</title> 586<title>Updating from profiles older than 1.4 to 1.4</title>
268</body> 594</body>
269</section> 595</section>
270</chapter> 596</chapter>
271 597
272</guide> 598</guide>
273

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.25

  ViewVC Help
Powered by ViewVC 1.1.20