/[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.18 Revision 1.37
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.18 2005/01/25 11:48:14 neysx Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.37 2007/05/07 18:11:40 nightmorph 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="greg_g@gentoo.org">Gregorio Guidi</mail> 9 <mail link="greg_g@gentoo.org">Gregorio Guidi</mail>
10</author> 10</author>
11<author title="Editor">
12 <mail link="wolf31o2@gentoo.org">Chris Gianelloni</mail>
13</author>
14<author title="Editor">
15 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
16</author>
11 17
12<abstract> 18<abstract>
13This document explains how new Gentoo releases affect existing installs. 19This document explains how new Gentoo releases affect existing installs.
14</abstract> 20</abstract>
15 21
16<!-- The content of this document is licensed under the CC-BY-SA license --> 22<!-- The content of this document is licensed under the CC-BY-SA license -->
17<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> 23<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
18<license/> 24<license/>
19 25
20<version>2.8</version> 26<version>2.8</version>
21<date>2005-01-22</date> 27<date>2007-05-05</date>
22 28
23<chapter> 29<chapter>
24<title>Gentoo and Upgrades</title> 30<title>Gentoo and Upgrades</title>
25<section> 31<section>
26<title>Philosophy</title> 32<title>Philosophy</title>
37<p> 43<p>
38You know (being a Gentoo user after all) that this process is extremely 44You 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 45frustrating for power users that want to live on the bleeding edge. Even power
40users from other distributions probably share the same feelings, given the 46users from other distributions probably share the same feelings, given the
41popularity and spread of tools like apt or apt-rpm which make it 47popularity and spread of tools like apt or apt-rpm which make it
42possible to have quick and frequent updates. However, no distibution is more 48possible to have quick and frequent updates. However, no distribution is more
43suited than Gentoo to satisfy these kind of demanding users. From the beginning, 49suited than Gentoo to satisfy these kind of demanding users. From the
44Gentoo was designed around the concept of fast, incremental updates. 50beginning, Gentoo was designed around the concept of fast, incremental
51updates.
45</p> 52</p>
46 53
47<p> 54<p>
48Ideally, you install once and never bother with releases: just follow the 55Ideally, you install once and never bother with releases: just follow the
49instructions in <uri 56instructions in <uri
66There are various reasons: 73There are various reasons:
67</p> 74</p>
68 75
69<ul> 76<ul>
70 <li> 77 <li>
71 A new release means new LiveCDs with bugfixes and more features. 78 A new release means new Installation CDs with bugfixes and more features.
72 </li> 79 </li>
73 <li> 80 <li>
74 A new release provides an updated set of GRP packages, so that users that 81 A new release provides an updated set of GRP packages, so that users that
75 choose "the fast way" to install (stage3 + precompiled packages) end up 82 choose "the fast way" to install (stage3 + precompiled packages) end up
76 with a system that is not outdated. 83 with a system that is not outdated.
95</p> 102</p>
96 103
97<p> 104<p>
98The profile in use is determined by the symbolic link 105The profile in use is determined by the symbolic link
99<path>/etc/make.profile</path>, which points to a subdirectory of 106<path>/etc/make.profile</path>, which points to a subdirectory of
100<path>/usr/portage/profiles</path> which holds the profile files. For instance, 107<path>/usr/portage/profiles</path> which holds the profile files. For
101the x86 2004.2 profile can be found at <path>/usr/portage/profiles/default-x86-2004.2</path> 108instance, the default x86 2007.0 profile can be found
102(old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style 109at <path>/usr/portage/profiles/default-linux/x86/2007.0</path>.
103location - only for use with Portage 2.0.51 and later). With respect to new-style profile directories, note that the files in 110The files in the parent directories are part of the profile as well (and
104parent directories are part of the profile (and are therefore shared 111are therefore shared by different subprofiles). This is why we call these
105by different subprofiles). 112<e>cascaded profiles</e>.
106</p> 113</p>
107 114
108<p> 115<p>
109Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> 116Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path>
110along with the current ones, but they are marked as deprecated. When that happens a 117along with the current ones, but they are marked as deprecated. When that
111file named <path>deprecated</path> is put in the profile directory. The content 118happens a file named <path>deprecated</path> is put in the profile directory.
112of this file is the name of the profile that should be "upgraded to"; portage uses 119The content of this file is the name of the profile that should be "upgraded
113this information to automatically warn you when you should update to a new profile. 120to"; portage uses this information to automatically warn you when you should
114</p> 121update to a new profile.
115
116<p> 122</p>
123
124<p>
117There are various reasons that a new profile may be created: the release of new 125There are various reasons that a new profile may be created: the release of
118versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or <c>glibc</c>) 126new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or
119that are incompatible with previous versions, a change in the default USE flags or 127<c>glibc</c>) that are incompatible with previous versions, a change in
120in the virtual mappings, or maybe a change in system-wide settings (such as defining 128the default USE flags or in the virtual mappings, or maybe a change in
121udev to be the default manager for <path>/dev</path> instead of devfs). 129system-wide settings.
122</p> 130</p>
123 131
124</body> 132</body>
125</section> 133</section>
126</chapter> 134</chapter>
130<section> 138<section>
131<title>Releases without profile changes</title> 139<title>Releases without profile changes</title>
132<body> 140<body>
133 141
134<p> 142<p>
135If a new Gentoo release is announced that does not include a new profile (such 143If a new Gentoo release is announced that does not include a new profile
136as the 2004.1 release for x86), then you can safely pretend that it never 144then you can safely pretend that it never happened :).
137happened :).
138</p> 145</p>
139 146
140<p> 147<p>
141If you update your installed packages 148If you update your installed packages
142<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in 149<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
149<section> 156<section>
150<title>Releases with profile changes</title> 157<title>Releases with profile changes</title>
151<body> 158<body>
152 159
153<p> 160<p>
154If a release introduces a new profile, you have the choice to migrate to the 161If a release (such as 2007.0 for x86) introduces a new profile, you have the
155new profile. 162choice to migrate to the new profile.
156</p>
157
158<p> 163</p>
164
165<p>
159Naturally, you are not forced to do so, and you can continue to use the old profile 166Naturally, you are not forced to do so, and you can continue to use the old
160and just update your packages 167profile and just update your packages
161<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in 168<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained
162the Gentoo Handbook</uri>. 169in the Gentoo Handbook</uri>.
163</p>
164
165<p> 170</p>
171
172<p>
166However, Gentoo strongly recommends updating your profile if it becomes deprecated. 173However, Gentoo strongly recommends updating your profile if it becomes
167When this happens, it means that Gentoo developers no longer plan on supporting it. 174deprecated. When this happens, it means that Gentoo developers no longer
168Using the table below, you can quickly check to see what profiles are currently supported. 175plan on supporting it. Using the table below, you can quickly check to
176see what profiles are currently supported.
169</p> 177</p>
170 178
171<p> 179<p>
172If you decide to migrate to the new profile, then you will have to manually 180If you decide to migrate to the new profile, then you will have to manually
173perform the update. The way you update may vary significantly from release to release; it 181perform the update. The way you update may vary significantly from release
174depends on how deep the modifications introduced in the new profile are. 182to release; it depends on how deep the modifications introduced in the new
183profile are.
175</p> 184</p>
176 185
177<p> 186<p>
178In the simplest case you only have to change the <path>/etc/make.profile</path> 187In the simplest case you only have to change the <path>/etc/make.profile</path>
179symlink, in the worst case you may have to recompile your system from scratch 188symlink, in the worst case you may have to recompile your system from scratch
180while doing a neat voodoo dance. Migration is usually covered in the release 189while doing a neat voodoo dance. Migration is usually covered in the release
181notes (e.g. <uri 190notes. You can also find <uri link="#instructions">instructions</uri> at the
182link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3 191end of this guide.
183release notes</uri>). You can also find <uri
184link="#instructions">instructions</uri> at the end of this guide.
185</p> 192</p>
186 193
187</body> 194</body>
188</section> 195</section>
189<section> 196<section>
190<title>Supported profiles</title> 197<title>Supported profiles</title>
191<body> 198<body>
192 199
193<p> 200<p>
194The following profiles are officially supported by Gentoo developers: 201You can view the list of profiles on your architecture officially supported by
202Gentoo developers when you <c>emerge eselect</c> and then run the following
203command:
204</p>
205
206<pre caption="Viewing supported profiles">
207# <i>eselect profile list</i>
195</p> 208</pre>
196
197<table>
198<tr>
199 <th>Architecture</th>
200 <th>Most recent profile</th>
201 <th>Other supported profiles</th>
202</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>
249 <th>x86</th>
250 <ti>2004.3</ti>
251 <ti>2004.2, 2004.0</ti>
252</tr>
253</table>
254 209
255</body> 210</body>
256</section> 211</section>
257</chapter> 212</chapter>
258 213
259<chapter id="instructions"> 214<chapter id="instructions">
260<title>Profile updating instructions</title> 215<title>Profile updating instructions</title>
216<section id="general">
217<title>General instructions</title>
218<body>
219
220<impo>
221Make sure your Portage is updated before performing any profile changes.
222</impo>
223
224<p>
225First, run <c>emerge eselect</c>. The <c>eselect</c> utility will let you view
226and select profiles easily, without needing to create or remove symlinks by
227hand.
228</p>
229
230<pre caption="Profile selection with eselect">
231<comment>(View available profiles)</comment>
232# <i>eselect profile list</i>
233
234<comment>(Select the number of your desired profile from the list)</comment>
235# <i>eselect profile set &lt;number&gt;</i>
236</pre>
237
238<p>
239If you'd still prefer to change profiles manually, then simply do the following:
240</p>
241
242<pre caption="Changing profiles manually">
243# <i>rm /etc/make.profile</i>
244# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
245</pre>
246
247<note>
248There are <b>desktop</b> and <b>server</b> subprofiles for most architectures.
249Examine these profiles carefully, as they may serve your needs better than the
250extremely minimal default profiles.
251</note>
252
253</body>
254</section>
255<section>
256<title>Updating to 2007.0 or 2006.1</title>
257<body>
258
259<p>
260If you intend to upgrade to these profiles, you should be aware that they expect
261the system to be set to a Unicode locale by default; specifically that
262UNICODE="yes" is set in <path>/etc/rc.conf</path>. For this to work, you must
263have created a Unicode locale for your system to use. Please read our <uri
264link="/doc/en/utf-8.xml">UTF-8 guide</uri> to learn how to create the proper
265locale.
266</p>
267
268<p>
269Alternatively, if you do not wish to set a locale, you should specify
270UNICODE="no" in <path>/etc/rc.conf</path>, and re-emerge <c>baselayout</c> (or
271wait until your next <c>baselayout</c> update) with the <c>-unicode</c> USE
272flag. You can set <c>-unicode</c> just for <c>baselayout</c>, or you can set it
273globally for all packages by adding it to your USE variable in
274<path>/etc/make.conf</path>.
275</p>
276
277<pre caption="Optional: removing Unicode support">
278<comment>(To remove Unicode support just for baselayout)</comment>
279# <i>echo "sys-apps/baselayout -unicode" >> /etc/portage/package.use</i>
280# <i>emerge -a baselayout</i>
281
282<comment>(To remove Unicode support from your whole system)</comment>
283# <i>nano -w /etc/make.conf</i>
284USE="-unicode"
285# <i>emerge -a baselayout</i>
286</pre>
287
288<note>
289If you are updating to a 2007.0 profile on the Sparc architecture, then you will
290need to follow the <uri link="/doc/en/gcc-upgrading.xml">GCC Upgrading
291Guide</uri>, as <c>gcc-4</c> is the default compiler.
292</note>
293
294<p>
295Finally, follow the <uri link="#general">general instructions</uri> for updating
296your profile.
297</p>
298
299</body>
300</section>
301<section>
302<title>Updating to 2006.0</title>
303<body>
304
305<p>
306To switch to the 2006.0 profile, point the <path>/etc/make.profile</path>
307symlink to the new location. Make sure your Portage is updated before you
308change your profile.
309</p>
310
311<pre caption="Changing to a 2006.0 profile">
312# <i>rm /etc/make.profile</i>
313# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
314</pre>
315
316<p>
317<b>alpha</b> - Users that use a 2.4 kernel or don't want to use NPTL should use
318the default-linux/alpha/no-nptl profile. More information is available in <uri
319link="/proj/en/releng/release/2006.0/alpha-release-notes.xml">the alpha release
320notes</uri>.
321</p>
322
323<p>
324<b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The ppc32
325profile has been changed in a way that offers a minimalistic generic profile
326for all purposes, located in default-linux/ppc/ppc32. The release-dependent
327profile is optimized for desktop-usage and located in
328default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and
329G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop
330Workstation. Make sure you choose the correct subprofile for your system when
331migrating to a 2006.0 profile.
332</p>
333
334<p>
335<b>sparc</b> - Upgrading to the <b>2.4</b>-kernel based 2006.0/2.4 profile
336requires manual user intervention (unmerging java stuff) and an <c>emerge -e
337world</c> because of the <uri link="/doc/en/gcc-upgrading.xml">gcc
338upgrade</uri>.<br/>
339Upgrading to the <b>2.6</b>-kernel based 2006.0 profile which is not considered
340stable also requires an entry in <path>/etc/portage/package.unmask</path> to
341umask a 2.6 version of <c>gentoo-sources</c> and a full rebuild.
342</p>
343
344<p>
345<b>All other archs</b> - There are no fundamental changes in this profile. No
346specific action needs to be performed.
347</p>
348
349</body>
350</section>
351<section>
352<title>Updating to 2005.1</title>
353<body>
354
355<p>
356To switch to the 2005.1 profile, point the <path>/etc/make.profile</path>
357symlink to the new location. Make sure your Portage is updated before you
358change your profile.
359</p>
360
361<pre caption="Changing to a 2005.1 profile">
362# <i>rm /etc/make.profile</i>
363# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
364</pre>
365
366<p>
367<b>All archs</b> - There are no fundamental changes in this profile. No
368specific action needs to be performed.
369</p>
370
371<p>
372<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged
373and a number of subprofiles for specific subarchitectures were created. Make
374sure you choose the correct subprofile for your system when migrating to a
3752005.1 profile.
376</p>
377
378</body>
379</section>
380<section>
381<title>Updating to 2005.0</title>
382<body>
383
384<p>
385With the introduction of 2005.0, several architectures have decided to define
386additional profiles. Make sure you read the description of said profiles before
387you decide to migrate to one of them. Most architectures now also default to the
3882.6 kernel tree where 2.4 was chosen previously.
389</p>
390
391<p>
392Some architectures require a bit more actions to be completed in order to
393convert from one profile to another. If that is the case, the step-by-step
394guides are linked from the table.
395</p>
396
397<table>
398<tr>
399 <th>Profile</th>
400 <th>Description</th>
401 <th>Specific Upgrade Guide</th>
402</tr>
403<tr>
404 <ti>default-linux/alpha/2005.0</ti>
405 <ti>Default Alpha 2005.0 profile for 2.6 kernels</ti>
406 <ti></ti>
407</tr>
408<tr>
409 <ti>default-linux/alpha/2005.0/2.4</ti>
410 <ti>Alpha 2005.0 profile for 2.4 kernels</ti>
411 <ti></ti>
412</tr>
413<tr>
414 <ti>default-linux/amd64/2005.0</ti>
415 <ti>Default AMD64 2005.0 profile for 2.6 kernels</ti>
416 <ti></ti>
417</tr>
418<tr>
419 <ti>default-linux/amd64/2005.0/no-multilib</ti>
420 <ti>AMD64 2005.0 profile for multilib-disabled system installations</ti>
421 <ti></ti>
422</tr>
423<tr>
424 <ti>default-linux/arm/2005.0</ti>
425 <ti>Default ARM 2005.0 profile for 2.6 kernels</ti>
426 <ti></ti>
427</tr>
428<tr>
429 <ti>default-linux/hppa/2005.0</ti>
430 <ti>Default HPPA 2005.0 profile for 2.6 kernels</ti>
431 <ti></ti>
432</tr>
433<tr>
434 <ti>default-linux/hppa/2005.0/2.4</ti>
435 <ti>HPPA 2005.0 profile for 2.4 kernels</ti>
436 <ti></ti>
437</tr>
438<tr>
439 <ti>default-linux/mips/2005.0</ti>
440 <ti>Default MIPS 2005.0 profile</ti>
441 <ti></ti>
442</tr>
443<tr>
444 <ti>default-linux/mips/cobalt/2005.0</ti>
445 <ti>Cobalt specific MIPS 2005.0 profile</ti>
446 <ti></ti>
447</tr>
448<tr>
449 <ti>default-linux/mips/mips64/n32/2005.0</ti>
450 <ti>2005.0 profile for n32-supporting MIPS platforms</ti>
451 <ti></ti>
452</tr>
453<tr>
454 <ti>default-linux/mips/mips64/ip28/2005.0</ti>
455 <ti>Indigo2 Impact specific 64-bit 2005.0 profile</ti>
456 <ti></ti>
457</tr>
458<tr>
459 <ti>default-linux/mips/mips64/2005.0</ti>
460 <ti>64-bit MIPS 2005.0 profile</ti>
461 <ti></ti>
462</tr>
463<tr>
464 <ti>default-linux/ppc/2005.0</ti>
465 <ti>Default PPC 2005.0 profile for 2.6 kernels</ti>
466 <ti></ti>
467</tr>
468<tr>
469 <ti>default-linux/ppc64/2005.0</ti>
470 <ti>Default PPC64 2005.0 profile for 2.6 kernels</ti>
471 <ti></ti>
472</tr>
473<tr>
474 <ti>default-linux/s390/2005.0</ti>
475 <ti>Default S390 2005.0 profile</ti>
476 <ti></ti>
477</tr>
478<tr>
479 <ti>default-linux/sparc/sparc32/2005.0</ti>
480 <ti>Default Sparc 32-bit 2005.0 profile</ti>
481 <ti></ti>
482</tr>
483<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
484 No subprofiles for sparc
485<tr>
486 <ti>default-linux/sparc/sparc32/2005.0/2.6</ti>
487 <ti>Sparc 32-bit 2005.0 profile for 2.6 kernels</ti>
488 <ti></ti>
489</tr>
490-->
491<tr>
492 <ti>default-linux/sparc/sparc64/2005.0</ti>
493 <ti>Default Sparc 64-bit 2005.0 profile</ti>
494 <ti></ti>
495</tr>
496<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
497 No subprofiles for sparc
498<tr>
499 <ti>default-linux/sparc/sparc64/2005.0/2.6</ti>
500 <ti>Sparc 64-bit 2005.0 profile for 2.6 kernels</ti>
501 <ti></ti>
502</tr>
503-->
504<tr>
505 <ti>default-linux/x86/2005.0</ti>
506 <ti>Default x86 2005.0 profile for 2.6 kernels</ti>
507 <ti></ti>
508</tr>
509<tr>
510 <ti>default-linux/x86/2005.0/2.4</ti>
511 <ti>x86 2005.0 profile for 2.4 kernels</ti>
512 <ti></ti>
513</tr>
514</table>
515
516<p>
517To switch to the selected profile, point the <path>/etc/make.profile</path>
518symlink to the new location. Make sure your Portage is updated before you change
519your profile!
520</p>
521
522<pre caption="Changing to a 2005.0 profile">
523# <i>rm /etc/make.profile</i>
524# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
525</pre>
526
527<p>
528If you are running a Linux 2.4-based system but want to migrate to a 2.6-based
529kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo
530Linux 2.6 Migration Guide</uri>.
531</p>
532
533</body>
534</section>
261<section> 535<section>
262<title>Updating to 2004.3</title> 536<title>Updating to 2004.3</title>
263<body> 537<body>
264 538
265<p> 539<p>
297<path>/var/lib/portage/world</path> after the profile switch, or manually 571<path>/var/lib/portage/world</path> after the profile switch, or manually
298emerge them. 572emerge them.
299</p> 573</p>
300 574
301<p> 575<p>
302<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/devfs</c> 576<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of
303for newly installed machines. This has no effect on already installed machines, 577<c>sys-fs/devfs</c> for newly installed machines. This has no
304though. 578effect on already installed machines, though.
579</p>
580
581</body>
582</section>
583<section>
584<title>Updating Portage to Support Cascading Profiles</title>
585<body>
586
305</p> 587<p>
588Although this section does not seem to integrate well in this upgrading guide,
589it is quite important. Any profile listed above this section requires a Portage
590version that supports cascading profiles. However, some obsoleted profiles don't
591allow the user to upgrade Portage or the user is using a profile that isn't
592available anymore - any attempt to upgrade Portage will result in a failure.
593</p>
594
595<p>
596To work around this problem, users can set a temporary symbolic link to the
597<e>obsolete</e> profile, allowing them to upgrade their Portage after which
598they can continue with the upgrade procedure set forth in this guide. Please
599substitute <c>&lt;arch&gt;</c> with your respective architecture:
600</p>
601
602<pre caption="Updating Portage through the obsolete profile">
603# <i>rm /etc/make.profile</i>
604# <i>cd /etc</i>
605# <i>ln -sf ../usr/portage/profiles/obsolete/&lt;arch&gt; make.profile</i>
606# <i>emerge -n '>=sys-apps/portage-2.0.51'</i>
607</pre>
306 608
307</body> 609</body>
308</section> 610</section>
309<section> 611<section>
310<title>Updating to 2004.2</title> 612<title>Updating to 2004.2</title>
311<body> 613<body>
312 614
313<p> 615<p>
314To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink 616To switch to the 2004.2 profile, point the <path>/etc/make.profile</path>
315to the new location: 617symlink to the new location:
316</p> 618</p>
317 619
318<warn> 620<warn>
319Don't forget to upgrade Portage <e>before</e> you change your profile!!! 621Don't forget to upgrade Portage <e>before</e> you change your profile!!!
320</warn> 622</warn>
344<section> 646<section>
345<title>Updating to 2004.0</title> 647<title>Updating to 2004.0</title>
346<body> 648<body>
347 649
348<p> 650<p>
349To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> symlink 651To switch to the 2004.0 profile, point the <path>/etc/make.profile</path>
350to the new location: 652symlink to the new location:
351</p> 653</p>
352 654
353<pre caption="Updating the /etc/make.profile symlink"> 655<pre caption="Updating the /etc/make.profile symlink">
354<comment>substitute &lt;arch&gt; with your arch</comment> 656<comment>substitute &lt;arch&gt; with your arch</comment>
355# <i>rm /etc/make.profile</i> 657# <i>rm /etc/make.profile</i>

Legend:
Removed from v.1.18  
changed lines
  Added in v.1.37

  ViewVC Help
Powered by ViewVC 1.1.20