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

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

  ViewVC Help
Powered by ViewVC 1.1.20