/[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.44
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.44 2012/10/31 18:17:54 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> 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 to react when a new Gentoo release is announced. 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>1.1</version> 26<version>4</version>
21<date>May 12, 2004</date> 27<date>2012-10-31</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>
27<body> 33<body>
28 34
29<p> 35<p>
30Here in Gentoo land, the concept of upgrade is quite different with respect to 36Here 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 37the 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 38touch with the "classic" way of upgrading software: waiting for a new release,
33latest version: waiting for a new release, downloading it, burning, putting it 39downloading it, burning, putting it in the cdrom drive and then following the
34in the cdrom drive and then following the upgrade instructions. 40upgrade instructions.
35</p>
36
37<p> 41</p>
42
43<p>
38You know (you chose Gentoo, 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 must share the same feelings, given the 46users 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 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, because Gentoo was 49suited than Gentoo to satisfy these kind of demanding users. From the
44shaped from the beginning 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>
48Ideally, you install once and then do not bother anymore about releases: 53
49just follow the instructions in 54<p>
55Ideally, you install once and never bother with releases: just follow the
56instructions in <uri
50<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">Portage and 57link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage
51Software</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 go usually, it can 60usually go, sometimes changes are made to the core system which require updates
54happen sometimes that developers push out, together with a new release, an 61to be done manually.
55update that touches the basics of the systems. We will consider these cases
56below, when talking about profiles.
57</p> 62</p>
58 63
59</body> 64</body>
60</section> 65</section>
61<section> 66<section>
62<title>Releases and Profiles</title> 67<title>Releases and Profiles</title>
63<body> 68<body>
64 69
65<p> 70<p>
66A 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
67releases frequently, if they are not intended to let users update software?". 72releases frequently, if they are not intended to let users update software?"
68There are various reasons: 73There are various reasons:
69</p> 74</p>
70 75
71<ul> 76<ul>
72 <li> 77 <li>
73 A new release means enhanced and more feature-rich LiveCDs. 78 A new release means new Installation CDs with bugfixes and more features
74 </li> 79 </li>
75 <li> 80 <li>
76 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
77 choose "the fast way" to install, stage3 + precompiled packages, end up 82 choose "the fast way" to install (stage3 + precompiled packages) end up
78 with a system that is not outdated. 83 with a system that is not outdated
79 </li> 84 </li>
80 <li> 85 <li>
81 Finally, a new release may (not frequently) implement some features that 86 Finally, a new release may, from time to time, implement some features that
82 are incompatible with previous releases. 87 are incompatible with previous releases
83 </li> 88 </li>
84</ul> 89</ul>
85 90
86<p> 91<p>
87When a release provides new incompatible features, or provides a set of core 92When 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 93packages 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>. 94that it provides a new <e>profile</e>.
91</p> 95</p>
92 96
93<p> 97<p>
94A <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
95<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
96that 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
97mapping for virtual packages. 101mapping for virtual packages, and the architecture on which the system is running.
98</p> 102</p>
99 103
100<p> 104<p>
101The profile in use is determined by the symbolic link 105The profile in use is determined by the symbolic link
102<path>/etc/make.profile</path>, which points to the subdirectory of 106<path>/etc/portage/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>. 107<path>/usr/portage/profiles</path> which holds the profile files. For
108instance, the default x86 2008.0 profile can be found
109at <path>/usr/portage/profiles/default/linux/x86/2008.0</path>.
110The files in the parent directories are part of the profile as well (and
111are therefore shared by different subprofiles). This is why we call these
112<e>cascaded profiles</e>.
104</p> 113</p>
105 114
106<p> 115<p>
107Profiles 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>
108as 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
109file 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.
110of this file is the name of the profile that should substitute it; portage uses 119The content of this file is the name of the profile that should be "upgraded
111this information to automatically warn you about the new profile. 120to"; Portage uses this information to automatically warn you when you should
112</p> 121update to a new profile.
113
114<p> 122</p>
115There are various reasons that justify the creation of a new profile: the 123
124<p>
125There 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> 126new 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 127<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 128the 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> 129system-wide settings.
120instead of devfs).
121</p> 130</p>
122 131
123</body> 132</body>
124</section> 133</section>
125</chapter> 134</chapter>
129<section> 138<section>
130<title>Releases without profile changes</title> 139<title>Releases without profile changes</title>
131<body> 140<body>
132 141
133<p> 142<p>
134If 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
135as the 2004.1 release for x86), then you can safely pretend that it never 144pretend that it never happened. :)
136happened.
137</p>
138
139<p> 145</p>
146
147<p>
140If you update your installed packages 148If you update your installed packages
141<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">as explained in 149<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 150the Gentoo Handbook</uri>, then your system will be exactly the same as one
143that has been installed using the new release. 151that has been installed using the new release.
144</p> 152</p>
145 153
146</body> 154</body>
148<section> 156<section>
149<title>Releases with profile changes</title> 157<title>Releases with profile changes</title>
150<body> 158<body>
151 159
152<p> 160<p>
153If 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
154new profile. 162choice to migrate to the new profile.
155</p>
156
157<p> 163</p>
164
165<p>
158Naturally, you are not forced to do so, you can continue to use the old profile 166Naturally, you are not forced to do so, and you can continue to use the old
159and just update your packages 167profile and just update your packages
160<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">as explained in 168<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). 169in the Gentoo Handbook</uri>.
162</p>
163
164<p> 170</p>
171
172<p>
165However, Gentoo strongly recommends a migration if your profile becomes 173However, Gentoo strongly recommends updating your profile if it becomes
166deprecated and is no more supported by Gentoo developers, that is to say that 174deprecated. When this happens, it means that Gentoo developers no longer
167your profile is not listed anymore in the table below. 175plan on supporting it.
168</p> 176</p>
169 177
170<p> 178<p>
171If 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
172perform some actions. Those actions may vary a lot from release to release, it 180perform the update. The way you update may vary significantly from release
173depends on how deep the modifications introduced in the new profile are. 181to release; it depends on how deep the modifications introduced in the new
174</p> 182profile are.
175
176<p> 183</p>
184
185<p>
177In 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>
178link, 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
179while doing some voodoo stuff. In every case we will publish the instructions 188while 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 189notes. You can also find <uri link="#instructions">instructions</uri> at the
181at the end of this guide. 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>cd /etc/portage</i>
244# <i>ln -s ../../usr/portage/profiles/</i>&lt;selected profile&gt;<i> 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<note>
254The <c>developer</c> subprofile is specifically for Gentoo Linux development
255tasks. It is <e>not</e> meant to help set up general development environments.
256</note>
257
258</body>
259</section>
260<section>
261<title>Updating to 2008.0, 2007.0, or 2006.1</title>
262<body>
263
264<p>
265If you intend to upgrade to these profiles, you should be aware that they expect
266the system to be set to a Unicode locale by default; specifically that
267UNICODE="yes" is set in <path>/etc/rc.conf</path>. For this to work, you must
268have created a Unicode locale for your system to use. Please read our <uri
269link="/doc/en/utf-8.xml">UTF-8 guide</uri> to learn how to create the proper
270locale.
271</p>
272
273<p>
274Alternatively, if you do not wish to set a locale, you should specify
275UNICODE="no" in <path>/etc/rc.conf</path>, and re-emerge <c>baselayout</c> (or
276wait until your next <c>baselayout</c> update) with the <c>-unicode</c> USE
277flag. You can set <c>-unicode</c> just for <c>baselayout</c>, or you can set it
278globally for all packages by adding it to your USE variable in
279<path>/etc/portage/make.conf</path>.
280</p>
281
282<pre caption="Optional: removing Unicode support">
283<comment>(To remove Unicode support just for baselayout)</comment>
284# <i>echo "sys-apps/baselayout -unicode" >> /etc/portage/package.use</i>
285# <i>emerge -a baselayout</i>
286
287<comment>(To remove Unicode support from your whole system)</comment>
288# <i>nano -w /etc/portage/make.conf</i>
289USE="-unicode"
290# <i>emerge -a baselayout</i>
291</pre>
292
293<note>
294If you are updating to a 2007.0 profile on the Sparc architecture, then you will
295need to follow the <uri link="/doc/en/gcc-upgrading.xml">GCC Upgrading
296Guide</uri>, as <c>gcc-4</c> is the default compiler.
297</note>
298
299<p>
300Finally, follow the <uri link="#general">general instructions</uri> for updating
301your profile.
302</p>
303
304</body>
305</section>
306<section>
307<title>Updating to 2006.0</title>
308<body>
309
310<p>
311To switch to the 2006.0 profile, point the <path>/etc/portage/make.profile</path>
312symlink to the new location. Make sure your Portage is updated before you
313change your profile.
314</p>
315
316<pre caption="Changing to a 2006.0 profile">
317# <i>rm /etc/portage/make.profile</i>
318# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/portage/make.profile</i>
319</pre>
320
321<p>
322<b>alpha</b> - Users that use a 2.4 kernel or don't want to use NPTL should use
323the default-linux/alpha/no-nptl profile. More information is available in <uri
324link="/proj/en/releng/release/2006.0/alpha-release-notes.xml">the alpha release
325notes</uri>.
326</p>
327
328<p>
329<b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The ppc32
330profile has been changed in a way that offers a minimalistic generic profile
331for all purposes, located in default-linux/ppc/ppc32. The release-dependent
332profile is optimized for desktop-usage and located in
333default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and
334G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop
335Workstation. Make sure you choose the correct subprofile for your system when
336migrating to a 2006.0 profile.
337</p>
338
339<p>
340<b>sparc</b> - Upgrading to the <b>2.4</b>-kernel based 2006.0/2.4 profile
341requires manual user intervention (unmerging java stuff) and an <c>emerge -e
342world</c> because of the <uri link="/doc/en/gcc-upgrading.xml">gcc
343upgrade</uri>.<br/>
344Upgrading to the <b>2.6</b>-kernel based 2006.0 profile which is not considered
345stable also requires an entry in <path>/etc/portage/package.unmask</path> to
346umask a 2.6 version of <c>gentoo-sources</c> and a full rebuild.
347</p>
348
349<p>
350<b>All other archs</b> - There are no fundamental changes in this profile. No
351specific action needs to be performed.
352</p>
353
354</body>
355</section>
356<section>
357<title>Updating to 2005.1</title>
358<body>
359
360<p>
361To switch to the 2005.1 profile, point the <path>/etc/portage/make.profile</path>
362symlink to the new location. Make sure your Portage is updated before you
363change your profile.
364</p>
365
366<pre caption="Changing to a 2005.1 profile">
367# <i>rm /etc/portage/make.profile</i>
368# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/portage/make.profile</i>
369</pre>
370
371<p>
372<b>All archs</b> - There are no fundamental changes in this profile. No
373specific action needs to be performed.
374</p>
375
376<p>
377<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged
378and a number of subprofiles for specific subarchitectures were created. Make
379sure you choose the correct subprofile for your system when migrating to a
3802005.1 profile.
381</p>
382
383</body>
384</section>
385<section>
386<title>Updating to 2005.0</title>
387<body>
388
389<p>
390With the introduction of 2005.0, several architectures have decided to define
391additional profiles. Make sure you read the description of said profiles before
392you decide to migrate to one of them. Most architectures now also default to the
3932.6 kernel tree where 2.4 was chosen previously.
394</p>
395
396<p>
397Some architectures require a bit more actions to be completed in order to
398convert from one profile to another. If that is the case, the step-by-step
399guides are linked from the table.
192</p> 400</p>
193 401
194<table> 402<table>
195<tr> 403<tr>
196 <th>Architecture</th> 404 <th>Profile</th>
197 <th>Most recent profile</th> 405 <th>Description</th>
198 <th>Other supported profiles</th> 406 <th>Specific Upgrade Guide</th>
199</tr>
200<tr> 407</tr>
201 <th>x86</th>
202 <ti>2004.0</ti>
203 <ti>1.4</ti>
204</tr> 408<tr>
409 <ti>default-linux/alpha/2005.0</ti>
410 <ti>Default Alpha 2005.0 profile for 2.6 kernels</ti>
411 <ti></ti>
205<tr> 412</tr>
206 <th>hardened-x86</th>
207 <ti>2004.0</ti>
208 <ti></ti>
209</tr> 413<tr>
414 <ti>default-linux/alpha/2005.0/2.4</ti>
415 <ti>Alpha 2005.0 profile for 2.4 kernels</ti>
416 <ti></ti>
210<tr> 417</tr>
211 <th>amd64</th>
212 <ti>2004.0</ti>
213 <ti></ti>
214</tr> 418<tr>
419 <ti>default-linux/amd64/2005.0</ti>
420 <ti>Default AMD64 2005.0 profile for 2.6 kernels</ti>
421 <ti></ti>
215<tr> 422</tr>
216 <th>ppc</th>
217 <ti>2004.0</ti>
218 <ti>1.4</ti>
219</tr> 423<tr>
424 <ti>default-linux/amd64/2005.0/no-multilib</ti>
425 <ti>AMD64 2005.0 profile for multilib-disabled system installations</ti>
426 <ti></ti>
220<tr> 427</tr>
221 <th>sparc</th>
222 <ti>2004.0</ti>
223 <ti>1.4</ti>
224</tr> 428<tr>
429 <ti>default-linux/arm/2005.0</ti>
430 <ti>Default ARM 2005.0 profile for 2.6 kernels</ti>
431 <ti></ti>
225<tr> 432</tr>
226 <th>mips</th>
227 <ti>2004.0</ti>
228 <ti>1.4</ti>
229</tr> 433<tr>
434 <ti>default-linux/hppa/2005.0</ti>
435 <ti>Default HPPA 2005.0 profile for 2.6 kernels</ti>
436 <ti></ti>
230<tr> 437</tr>
231 <th>hppa</th> 438<tr>
439 <ti>default-linux/hppa/2005.0/2.4</ti>
440 <ti>HPPA 2005.0 profile for 2.4 kernels</ti>
232 <ti>2004.0</ti> 441 <ti></ti>
442</tr>
443<tr>
444 <ti>default-linux/mips/2005.0</ti>
445 <ti>Default MIPS 2005.0 profile</ti>
446 <ti></ti>
447</tr>
448<tr>
449 <ti>default-linux/mips/cobalt/2005.0</ti>
450 <ti>Cobalt specific MIPS 2005.0 profile</ti>
451 <ti></ti>
452</tr>
453<tr>
454 <ti>default-linux/mips/mips64/n32/2005.0</ti>
455 <ti>2005.0 profile for n32-supporting MIPS platforms</ti>
456 <ti></ti>
457</tr>
458<tr>
459 <ti>default-linux/mips/mips64/ip28/2005.0</ti>
460 <ti>Indigo2 Impact specific 64-bit 2005.0 profile</ti>
461 <ti></ti>
462</tr>
463<tr>
464 <ti>default-linux/mips/mips64/2005.0</ti>
465 <ti>64-bit MIPS 2005.0 profile</ti>
466 <ti></ti>
467</tr>
468<tr>
469 <ti>default-linux/ppc/2005.0</ti>
470 <ti>Default PPC 2005.0 profile for 2.6 kernels</ti>
471 <ti></ti>
472</tr>
473<tr>
474 <ti>default-linux/ppc64/2005.0</ti>
475 <ti>Default PPC64 2005.0 profile for 2.6 kernels</ti>
476 <ti></ti>
477</tr>
478<tr>
479 <ti>default-linux/s390/2005.0</ti>
480 <ti>Default S390 2005.0 profile</ti>
481 <ti></ti>
482</tr>
483<tr>
484 <ti>default-linux/sparc/sparc32/2005.0</ti>
485 <ti>Default Sparc 32-bit 2005.0 profile</ti>
486 <ti></ti>
487</tr>
488<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
489 No subprofiles for sparc
490<tr>
491 <ti>default-linux/sparc/sparc32/2005.0/2.6</ti>
492 <ti>Sparc 32-bit 2005.0 profile for 2.6 kernels</ti>
493 <ti></ti>
494</tr>
495-->
496<tr>
497 <ti>default-linux/sparc/sparc64/2005.0</ti>
498 <ti>Default Sparc 64-bit 2005.0 profile</ti>
499 <ti></ti>
500</tr>
501<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
502 No subprofiles for sparc
503<tr>
504 <ti>default-linux/sparc/sparc64/2005.0/2.6</ti>
505 <ti>Sparc 64-bit 2005.0 profile for 2.6 kernels</ti>
506 <ti></ti>
507</tr>
508-->
509<tr>
510 <ti>default-linux/x86/2005.0</ti>
511 <ti>Default x86 2005.0 profile for 2.6 kernels</ti>
512 <ti></ti>
513</tr>
514<tr>
515 <ti>default-linux/x86/2005.0/2.4</ti>
516 <ti>x86 2005.0 profile for 2.4 kernels</ti>
233 <ti></ti> 517 <ti></ti>
234</tr> 518</tr>
235</table> 519</table>
236 520
237</body> 521<p>
238</section> 522To switch to the selected profile, point the <path>/etc/portage/make.profile</path>
239</chapter> 523symlink to the new location. Make sure your Portage is updated before you change
524your profile!
525</p>
240 526
241<chapter> 527<pre caption="Changing to a 2005.0 profile">
242<title>Profile updating instructions</title> 528# <i>rm /etc/portage/make.profile</i>
529# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/portage/make.profile</i>
530</pre>
531
532<p>
533If you are running a Linux 2.4-based system but want to migrate to a 2.6-based
534kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo
535Linux 2.6 Migration Guide</uri>.
536</p>
537
538</body>
243<section> 539</section>
244<title>Updating from 1.4 to 2004.0 (all archs)</title> 540<section>
541<title>Updating to 2004.3</title>
542<body>
543
544<p>
545With the introduction of the 2004.3 profiles, users are not going to see huge
546modifications of their systems (see below for details). However, Gentoo
547developers decided to push out this new profile and to deprecate quite a few of
548the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the
549profiles that follow the new layout of the <path>/usr/portage/profiles</path>
550directory, for instance
551<path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
552Portage 2.0.51 or later).
553</p>
554
555<p>
556To switch to the 2004.3 profile, point the <path>/etc/portage/make.profile</path>
557symlink to the new location:
558</p>
559
560<warn>
561Don't forget to upgrade Portage <e>before</e> you change your profile!!!
562</warn>
563
564<pre caption="Updating the /etc/portage/make.profile symlink">
565<comment>substitute &lt;arch&gt; with your arch</comment>
566# <i>rm /etc/portage/make.profile</i>
567# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/portage/make.profile</i>
568</pre>
569
570<p>
571<b>All archs</b> - As said above, there are no big changes introduced in this
572profile. However, it should be noted that <c>sys-apps/slocate</c> and
573<c>net-misc/dhcpcd</c> are no longer considered system packages. This means
574that if you run <c>emerge --depclean</c>, Portage will try to remove them from
575your system. If you need any of those packages, add them to
576<path>/var/lib/portage/world</path> after the profile switch, or manually
577emerge them.
578</p>
579
580<p>
581<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of
582<c>sys-fs/devfs</c> for newly installed machines. This has no
583effect on already installed machines, though.
584</p>
585
245<body> 586</body>
587</section>
588<section>
589<title>Updating Portage to Support Cascading Profiles</title>
590<body>
246 591
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> 592<p>
593Although this section does not seem to integrate well in this upgrading guide,
594it is quite important. Any profile listed above this section requires a Portage
595version that supports cascading profiles. However, some obsoleted profiles don't
596allow the user to upgrade Portage or the user is using a profile that isn't
597available anymore - any attempt to upgrade Portage will result in a failure.
598</p>
251 599
600<p>
601To work around this problem, users can set a temporary symbolic link to the
602<e>obsolete</e> profile, allowing them to upgrade their Portage after which
603they can continue with the upgrade procedure set forth in this guide. Please
604substitute <c>&lt;arch&gt;</c> with your respective architecture:
605</p>
606
607<pre caption="Updating Portage through the obsolete profile">
608# <i>rm /etc/portage/make.profile</i>
609# <i>cd /etc/portage</i>
610# <i>ln -sf ../usr/portage/profiles/obsolete/&lt;arch&gt; make.profile</i>
611# <i>emerge -n '>=sys-apps/portage-2.0.51'</i>
612</pre>
613
614</body>
615</section>
616<section>
617<title>Updating to 2004.2</title>
618<body>
619
620<p>
621To switch to the 2004.2 profile, point the <path>/etc/portage/make.profile</path>
622symlink to the new location:
623</p>
624
625<warn>
626Don't forget to upgrade Portage <e>before</e> you change your profile!!!
627</warn>
628
252<pre caption="Updating the /etc/make.profile link"> 629<pre caption="Updating the /etc/portage/make.profile symlink">
630<comment>substitute &lt;arch&gt; with your arch</comment>
253# <i>rm /etc/make.profile</i> 631# <i>rm /etc/portage/make.profile</i>
632# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/portage/make.profile</i>
633</pre>
634
635<p>
636<b>x86</b> - This profile changes the default X11 implementation from
637<c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches
638the <e>default</e> value, and is only relevant for those who have not installed
639an X server yet. If you already have one installed, then it will not affect
640you at all; you are free to switch from one X server to the other exactly as
641before.
642</p>
643
644<p>
645<b>amd64</b> - There are no fundamental changes from previous profiles, no
646specific action needs to be performed.
647</p>
648
649</body>
650</section>
651<section>
652<title>Updating to 2004.0</title>
653<body>
654
655<p>
656To switch to the 2004.0 profile, point the <path>/etc/portage/make.profile</path>
657symlink to the new location:
658</p>
659
660<pre caption="Updating the /etc/portage/make.profile symlink">
661<comment>substitute &lt;arch&gt; with your arch</comment>
662# <i>rm /etc/portage/make.profile</i>
254# <i>ln -s ../usr/portage/profiles/default-x86-2004.0 /etc/make.profile</i> 663# <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/portage/make.profile</i>
664</pre>
665
666<p>
667<b>All archs</b> - There are no fundamental changes from previous profiles, no
668specific action needs to be performed.
255</pre> 669</p>
256 670
257</body> 671</body>
258</section> 672</section>
259<section> 673<section>
260<title>Updating from profiles older than 1.4 to 1.4</title> 674<title>Updating from profiles older than 1.4 to 1.4</title>
268</body> 682</body>
269</section> 683</section>
270</chapter> 684</chapter>
271 685
272</guide> 686</guide>
273

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

  ViewVC Help
Powered by ViewVC 1.1.20