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

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

  ViewVC Help
Powered by ViewVC 1.1.20