/[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.11 Revision 1.43
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.11 2004/10/24 22:48:37 neysx Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.43 2012/07/24 12:12:51 swift Exp $ -->
4 4
5<guide link="/doc/en/gentoo-upgrading.xml"> 5<guide>
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>
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>
10</author> 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/1.0 --> 23<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
18<license/> 24<license/>
19 25
20<version>2.3</version> 26<version>3</version>
21<date>September 25, 2004</date> 27<date>2012-07-24</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
45</p> 51updates.
46
47<p> 52</p>
53
54<p>
48Ideally, you install once and then do not to bother with releases: 55Ideally, you install once and never bother with releases: just follow the
49just follow the instructions in 56instructions in <uri
50<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage 57link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage
51Introduction</uri> in the 58Introduction</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 59that 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 usually go, sometimes 60usually go, sometimes changes are made to the core system which require updates
54changes are made to the core system which require updates to be done manually. 61to be done manually.
55</p> 62</p>
56 63
57</body> 64</body>
58</section> 65</section>
59<section> 66<section>
60<title>Releases and Profiles</title> 67<title>Releases and Profiles</title>
61<body> 68<body>
62 69
63<p> 70<p>
64A recurring question about the Gentoo release process is: "Why roll out new 71A recurring question about the Gentoo release process is: "Why roll out new
65releases frequently, if they are not intended to let users update software?". 72releases frequently, if they are not intended to let users update software?"
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) and 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
77 </li> 84 </li>
78 <li> 85 <li>
79 Finally, a new release may, from time to time, implement some features that 86 Finally, a new release may, from time to time, implement some features that
80 are incompatible with previous releases. 87 are incompatible with previous releases
81 </li> 88 </li>
82</ul> 89</ul>
83 90
84<p> 91<p>
85When a release includes new incompatible features, or provides a set of core 92When a release includes new incompatible features, or provides a set of core
87that it provides a new <e>profile</e>. 94that it provides a new <e>profile</e>.
88</p> 95</p>
89 96
90<p> 97<p>
91A <e>profile</e> is a set of configuration files, stored in a subdirectory of 98A <e>profile</e> is a set of configuration files, stored in a subdirectory of
92<path>/usr/portage/profiles/</path>, that describe things such as the ebuilds 99<path>/usr/portage/profiles</path>, that describe things such as the ebuilds
93that are considered <e>system</e> packages, the default USE flags, the default 100that are considered <e>system</e> packages, the default USE flags, the default
94mapping for virtual packages, and architecture that the system is running. 101mapping for virtual packages, and the architecture on which the system is running.
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/portage/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 2008.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/2008.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 does not include a new profile then you can safely
136as the 2004.1 release for x86), then you can safely pretend that it never 144pretend 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 2008.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.
169</p> 176</p>
170 177
171<p> 178<p>
172If you decide to migrate to the new profile, then you will have to manually 179If 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 180perform the update. The way you update may vary significantly from release
174depends on how deep the modifications introduced in the new profile. 181to release; it depends on how deep the modifications introduced in the new
175</p> 182profile are.
176
177<p> 183</p>
184
185<p>
178In the simplest case you only have to change the <path>/etc/make.profile</path> 186In the simplest case you only have to change the <path>/etc/portage/make.profile</path>
179symlink, in the worst case you may have to recompile your system from scratch 187symlink, in the worst case you may have to recompile your system from scratch
180while doing a neat voodoo dance. Regardless, we will publish migration instructions 188while doing a neat voodoo dance. Migration is usually covered in the release
181as part of the release. You can also find these instructions at the end of this guide. 189notes. You can also find <uri link="#instructions">instructions</uri> at the
190end of this guide.
182</p> 191</p>
183 192
184</body> 193</body>
185</section> 194</section>
186<section> 195<section>
187<title>Supported profiles</title> 196<title>Supported profiles</title>
188<body> 197<body>
189 198
190<p> 199<p>
191The following profiles are officially supported by Gentoo developers: 200You can view the list of profiles on your architecture officially supported by
201Gentoo developers when you <c>emerge eselect</c> and then run the following
202command:
203</p>
204
205<pre caption="Viewing supported profiles">
206# <i>eselect profile list</i>
207</pre>
208
209</body>
210</section>
211</chapter>
212
213<chapter id="instructions">
214<title>Profile updating instructions</title>
215<section id="general">
216<title>General instructions</title>
217<body>
218
219<impo>
220Make sure your Portage is updated before performing any profile changes.
221</impo>
222
223<p>
224First, run <c>emerge eselect</c>. The <c>eselect</c> utility will let you view
225and select profiles easily, without needing to create or remove symlinks by
226hand.
227</p>
228
229<pre caption="Profile selection with eselect">
230<comment>(View available profiles)</comment>
231# <i>eselect profile list</i>
232
233<comment>(Select the number of your desired profile from the list)</comment>
234# <i>eselect profile set &lt;number&gt;</i>
235</pre>
236
237<p>
238If you'd still prefer to change profiles manually, then simply do the following:
239</p>
240
241<pre caption="Changing profiles manually">
242# <i>rm /etc/portage/make.profile</i>
243# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/portage/make.profile</i>
244</pre>
245
246<note>
247There are <b>desktop</b> and <b>server</b> subprofiles for most architectures.
248Examine these profiles carefully, as they may serve your needs better than the
249extremely minimal default profiles.
250</note>
251
252<note>
253The <c>developer</c> subprofile is specifically for Gentoo Linux development
254tasks. It is <e>not</e> meant to help set up general development environments.
255</note>
256
257</body>
258</section>
259<section>
260<title>Updating to 2008.0, 2007.0, or 2006.1</title>
261<body>
262
263<p>
264If you intend to upgrade to these profiles, you should be aware that they expect
265the system to be set to a Unicode locale by default; specifically that
266UNICODE="yes" is set in <path>/etc/rc.conf</path>. For this to work, you must
267have created a Unicode locale for your system to use. Please read our <uri
268link="/doc/en/utf-8.xml">UTF-8 guide</uri> to learn how to create the proper
269locale.
270</p>
271
272<p>
273Alternatively, if you do not wish to set a locale, you should specify
274UNICODE="no" in <path>/etc/rc.conf</path>, and re-emerge <c>baselayout</c> (or
275wait until your next <c>baselayout</c> update) with the <c>-unicode</c> USE
276flag. You can set <c>-unicode</c> just for <c>baselayout</c>, or you can set it
277globally for all packages by adding it to your USE variable in
278<path>/etc/portage/make.conf</path>.
279</p>
280
281<pre caption="Optional: removing Unicode support">
282<comment>(To remove Unicode support just for baselayout)</comment>
283# <i>echo "sys-apps/baselayout -unicode" >> /etc/portage/package.use</i>
284# <i>emerge -a baselayout</i>
285
286<comment>(To remove Unicode support from your whole system)</comment>
287# <i>nano -w /etc/portage/make.conf</i>
288USE="-unicode"
289# <i>emerge -a baselayout</i>
290</pre>
291
292<note>
293If you are updating to a 2007.0 profile on the Sparc architecture, then you will
294need to follow the <uri link="/doc/en/gcc-upgrading.xml">GCC Upgrading
295Guide</uri>, as <c>gcc-4</c> is the default compiler.
296</note>
297
298<p>
299Finally, follow the <uri link="#general">general instructions</uri> for updating
300your profile.
301</p>
302
303</body>
304</section>
305<section>
306<title>Updating to 2006.0</title>
307<body>
308
309<p>
310To switch to the 2006.0 profile, point the <path>/etc/portage/make.profile</path>
311symlink to the new location. Make sure your Portage is updated before you
312change your profile.
313</p>
314
315<pre caption="Changing to a 2006.0 profile">
316# <i>rm /etc/portage/make.profile</i>
317# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/portage/make.profile</i>
318</pre>
319
320<p>
321<b>alpha</b> - Users that use a 2.4 kernel or don't want to use NPTL should use
322the default-linux/alpha/no-nptl profile. More information is available in <uri
323link="/proj/en/releng/release/2006.0/alpha-release-notes.xml">the alpha release
324notes</uri>.
325</p>
326
327<p>
328<b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The ppc32
329profile has been changed in a way that offers a minimalistic generic profile
330for all purposes, located in default-linux/ppc/ppc32. The release-dependent
331profile is optimized for desktop-usage and located in
332default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and
333G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop
334Workstation. Make sure you choose the correct subprofile for your system when
335migrating to a 2006.0 profile.
336</p>
337
338<p>
339<b>sparc</b> - Upgrading to the <b>2.4</b>-kernel based 2006.0/2.4 profile
340requires manual user intervention (unmerging java stuff) and an <c>emerge -e
341world</c> because of the <uri link="/doc/en/gcc-upgrading.xml">gcc
342upgrade</uri>.<br/>
343Upgrading to the <b>2.6</b>-kernel based 2006.0 profile which is not considered
344stable also requires an entry in <path>/etc/portage/package.unmask</path> to
345umask a 2.6 version of <c>gentoo-sources</c> and a full rebuild.
346</p>
347
348<p>
349<b>All other archs</b> - There are no fundamental changes in this profile. No
350specific action needs to be performed.
351</p>
352
353</body>
354</section>
355<section>
356<title>Updating to 2005.1</title>
357<body>
358
359<p>
360To switch to the 2005.1 profile, point the <path>/etc/portage/make.profile</path>
361symlink to the new location. Make sure your Portage is updated before you
362change your profile.
363</p>
364
365<pre caption="Changing to a 2005.1 profile">
366# <i>rm /etc/portage/make.profile</i>
367# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/portage/make.profile</i>
368</pre>
369
370<p>
371<b>All archs</b> - There are no fundamental changes in this profile. No
372specific action needs to be performed.
373</p>
374
375<p>
376<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged
377and a number of subprofiles for specific subarchitectures were created. Make
378sure you choose the correct subprofile for your system when migrating to a
3792005.1 profile.
380</p>
381
382</body>
383</section>
384<section>
385<title>Updating to 2005.0</title>
386<body>
387
388<p>
389With the introduction of 2005.0, several architectures have decided to define
390additional profiles. Make sure you read the description of said profiles before
391you decide to migrate to one of them. Most architectures now also default to the
3922.6 kernel tree where 2.4 was chosen previously.
393</p>
394
395<p>
396Some architectures require a bit more actions to be completed in order to
397convert from one profile to another. If that is the case, the step-by-step
398guides are linked from the table.
192</p> 399</p>
193 400
194<table> 401<table>
195<tr> 402<tr>
196 <th>Architecture</th> 403 <th>Profile</th>
197 <th>Most recent profile</th> 404 <th>Description</th>
198 <th>Other supported profiles</th> 405 <th>Specific Upgrade Guide</th>
199</tr>
200<tr> 406</tr>
201 <th>arm</th>
202 <ti>2004.0</ti>
203 <ti></ti>
204</tr> 407<tr>
408 <ti>default-linux/alpha/2005.0</ti>
409 <ti>Default Alpha 2005.0 profile for 2.6 kernels</ti>
410 <ti></ti>
205<tr> 411</tr>
206 <th>amd64</th>
207 <ti>2004.2</ti>
208 <ti>2004.0</ti>
209</tr> 412<tr>
413 <ti>default-linux/alpha/2005.0/2.4</ti>
414 <ti>Alpha 2005.0 profile for 2.4 kernels</ti>
415 <ti></ti>
210<tr> 416</tr>
211 <th>hardened-x86</th>
212 <ti>2004.0</ti>
213 <ti></ti>
214</tr> 417<tr>
418 <ti>default-linux/amd64/2005.0</ti>
419 <ti>Default AMD64 2005.0 profile for 2.6 kernels</ti>
420 <ti></ti>
215<tr> 421</tr>
216 <th>hppa</th>
217 <ti>2004.0</ti>
218 <ti></ti>
219</tr> 422<tr>
423 <ti>default-linux/amd64/2005.0/no-multilib</ti>
424 <ti>AMD64 2005.0 profile for multilib-disabled system installations</ti>
425 <ti></ti>
220<tr> 426</tr>
221 <th>ppc</th>
222 <ti>2004.0</ti>
223 <ti></ti>
224</tr> 427<tr>
428 <ti>default-linux/arm/2005.0</ti>
429 <ti>Default ARM 2005.0 profile for 2.6 kernels</ti>
430 <ti></ti>
225<tr> 431</tr>
226 <th>mips</th>
227 <ti>2004.1</ti>
228 <ti>1.4</ti>
229</tr> 432<tr>
433 <ti>default-linux/hppa/2005.0</ti>
434 <ti>Default HPPA 2005.0 profile for 2.6 kernels</ti>
435 <ti></ti>
230<tr> 436</tr>
231 <th>sparc</th>
232 <ti>2004.0</ti>
233 <ti></ti>
234</tr> 437<tr>
438 <ti>default-linux/hppa/2005.0/2.4</ti>
439 <ti>HPPA 2005.0 profile for 2.4 kernels</ti>
440 <ti></ti>
235<tr> 441</tr>
236 <th>sparc64</th>
237 <ti>2004.0</ti>
238 <ti></ti>
239</tr> 442<tr>
443 <ti>default-linux/mips/2005.0</ti>
444 <ti>Default MIPS 2005.0 profile</ti>
445 <ti></ti>
240<tr> 446</tr>
241 <th>x86</th> 447<tr>
448 <ti>default-linux/mips/cobalt/2005.0</ti>
449 <ti>Cobalt specific MIPS 2005.0 profile</ti>
242 <ti>2004.2</ti> 450 <ti></ti>
243 <ti>2004.0, 1.4</ti> 451</tr>
452<tr>
453 <ti>default-linux/mips/mips64/n32/2005.0</ti>
454 <ti>2005.0 profile for n32-supporting MIPS platforms</ti>
455 <ti></ti>
456</tr>
457<tr>
458 <ti>default-linux/mips/mips64/ip28/2005.0</ti>
459 <ti>Indigo2 Impact specific 64-bit 2005.0 profile</ti>
460 <ti></ti>
461</tr>
462<tr>
463 <ti>default-linux/mips/mips64/2005.0</ti>
464 <ti>64-bit MIPS 2005.0 profile</ti>
465 <ti></ti>
466</tr>
467<tr>
468 <ti>default-linux/ppc/2005.0</ti>
469 <ti>Default PPC 2005.0 profile for 2.6 kernels</ti>
470 <ti></ti>
471</tr>
472<tr>
473 <ti>default-linux/ppc64/2005.0</ti>
474 <ti>Default PPC64 2005.0 profile for 2.6 kernels</ti>
475 <ti></ti>
476</tr>
477<tr>
478 <ti>default-linux/s390/2005.0</ti>
479 <ti>Default S390 2005.0 profile</ti>
480 <ti></ti>
481</tr>
482<tr>
483 <ti>default-linux/sparc/sparc32/2005.0</ti>
484 <ti>Default Sparc 32-bit 2005.0 profile</ti>
485 <ti></ti>
486</tr>
487<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
488 No subprofiles for sparc
489<tr>
490 <ti>default-linux/sparc/sparc32/2005.0/2.6</ti>
491 <ti>Sparc 32-bit 2005.0 profile for 2.6 kernels</ti>
492 <ti></ti>
493</tr>
494-->
495<tr>
496 <ti>default-linux/sparc/sparc64/2005.0</ti>
497 <ti>Default Sparc 64-bit 2005.0 profile</ti>
498 <ti></ti>
499</tr>
500<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
501 No subprofiles for sparc
502<tr>
503 <ti>default-linux/sparc/sparc64/2005.0/2.6</ti>
504 <ti>Sparc 64-bit 2005.0 profile for 2.6 kernels</ti>
505 <ti></ti>
506</tr>
507-->
508<tr>
509 <ti>default-linux/x86/2005.0</ti>
510 <ti>Default x86 2005.0 profile for 2.6 kernels</ti>
511 <ti></ti>
512</tr>
513<tr>
514 <ti>default-linux/x86/2005.0/2.4</ti>
515 <ti>x86 2005.0 profile for 2.4 kernels</ti>
516 <ti></ti>
244</tr> 517</tr>
245</table> 518</table>
246 519
520<p>
521To switch to the selected profile, point the <path>/etc/portage/make.profile</path>
522symlink to the new location. Make sure your Portage is updated before you change
523your profile!
524</p>
525
526<pre caption="Changing to a 2005.0 profile">
527# <i>rm /etc/portage/make.profile</i>
528# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/portage/make.profile</i>
529</pre>
530
531<p>
532If you are running a Linux 2.4-based system but want to migrate to a 2.6-based
533kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo
534Linux 2.6 Migration Guide</uri>.
535</p>
536
247</body> 537</body>
538</section>
248</section> 539<section>
249</chapter> 540<title>Updating to 2004.3</title>
541<body>
250 542
251<chapter> 543<p>
252<title>Profile updating instructions</title> 544With the introduction of the 2004.3 profiles, users are not going to see huge
545modifications of their systems (see below for details). However, Gentoo
546developers decided to push out this new profile and to deprecate quite a few of
547the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the
548profiles that follow the new layout of the <path>/usr/portage/profiles</path>
549directory, for instance
550<path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
551Portage 2.0.51 or later).
552</p>
553
554<p>
555To switch to the 2004.3 profile, point the <path>/etc/portage/make.profile</path>
556symlink to the new location:
557</p>
558
559<warn>
560Don't forget to upgrade Portage <e>before</e> you change your profile!!!
561</warn>
562
563<pre caption="Updating the /etc/portage/make.profile symlink">
564<comment>substitute &lt;arch&gt; with your arch</comment>
565# <i>rm /etc/portage/make.profile</i>
566# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/portage/make.profile</i>
567</pre>
568
569<p>
570<b>All archs</b> - As said above, there are no big changes introduced in this
571profile. However, it should be noted that <c>sys-apps/slocate</c> and
572<c>net-misc/dhcpcd</c> are no longer considered system packages. This means
573that if you run <c>emerge --depclean</c>, Portage will try to remove them from
574your system. If you need any of those packages, add them to
575<path>/var/lib/portage/world</path> after the profile switch, or manually
576emerge them.
577</p>
578
579<p>
580<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of
581<c>sys-fs/devfs</c> for newly installed machines. This has no
582effect on already installed machines, though.
583</p>
584
585</body>
586</section>
587<section>
588<title>Updating Portage to Support Cascading Profiles</title>
589<body>
590
591<p>
592Although this section does not seem to integrate well in this upgrading guide,
593it is quite important. Any profile listed above this section requires a Portage
594version that supports cascading profiles. However, some obsoleted profiles don't
595allow the user to upgrade Portage or the user is using a profile that isn't
596available anymore - any attempt to upgrade Portage will result in a failure.
597</p>
598
599<p>
600To work around this problem, users can set a temporary symbolic link to the
601<e>obsolete</e> profile, allowing them to upgrade their Portage after which
602they can continue with the upgrade procedure set forth in this guide. Please
603substitute <c>&lt;arch&gt;</c> with your respective architecture:
604</p>
605
606<pre caption="Updating Portage through the obsolete profile">
607# <i>rm /etc/portage/make.profile</i>
608# <i>cd /etc/portage</i>
609# <i>ln -sf ../usr/portage/profiles/obsolete/&lt;arch&gt; make.profile</i>
610# <i>emerge -n '>=sys-apps/portage-2.0.51'</i>
611</pre>
612
613</body>
614</section>
253<section> 615<section>
254<title>Updating to 2004.2</title> 616<title>Updating to 2004.2</title>
255<body> 617<body>
256 618
257<p> 619<p>
258To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink 620To switch to the 2004.2 profile, point the <path>/etc/portage/make.profile</path>
259to the new location: 621symlink to the new location:
260</p> 622</p>
261 623
624<warn>
625Don't forget to upgrade Portage <e>before</e> you change your profile!!!
626</warn>
627
262<pre caption="Updating the /etc/make.profile symlink"> 628<pre caption="Updating the /etc/portage/make.profile symlink">
263<comment>substitute &lt;arch&gt; with your arch</comment> 629<comment>substitute &lt;arch&gt; with your arch</comment>
264# <i>rm /etc/make.profile</i> 630# <i>rm /etc/portage/make.profile</i>
265# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i> 631# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/portage/make.profile</i>
266</pre> 632</pre>
267 633
268<p> 634<p>
269<b>x86</b> - This profile changes the default X11 implementation from 635<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 636<c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches
284<section> 650<section>
285<title>Updating to 2004.0</title> 651<title>Updating to 2004.0</title>
286<body> 652<body>
287 653
288<p> 654<p>
289To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> symlink 655To switch to the 2004.0 profile, point the <path>/etc/portage/make.profile</path>
290to the new location: 656symlink to the new location:
291</p> 657</p>
292 658
293<pre caption="Updating the /etc/make.profile symlink"> 659<pre caption="Updating the /etc/portage/make.profile symlink">
294<comment>substitute &lt;arch&gt; with your arch</comment> 660<comment>substitute &lt;arch&gt; with your arch</comment>
295# <i>rm /etc/make.profile</i> 661# <i>rm /etc/portage/make.profile</i>
296# <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/make.profile</i> 662# <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/portage/make.profile</i>
297</pre> 663</pre>
298 664
299<p> 665<p>
300<b>All archs</b> - There are no fundamental changes from previous profiles, no 666<b>All archs</b> - There are no fundamental changes from previous profiles, no
301specific action needs to be performed. 667specific action needs to be performed.

Legend:
Removed from v.1.11  
changed lines
  Added in v.1.43

  ViewVC Help
Powered by ViewVC 1.1.20