/[gentoo]/xml/htdocs/doc/en/gentoo-upgrading.xml
Gentoo

Contents of /xml/htdocs/doc/en/gentoo-upgrading.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.33 - (show annotations) (download) (as text)
Sat Sep 2 16:22:24 2006 UTC (8 years ago) by neysx
Branch: MAIN
Changes since 1.32: +93 -21 lines
File MIME type: application/xml
#145731 take 1, Upgrading to 2006.1

1 <?xml version='1.0' encoding="UTF-8"?>
2 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.32 2006/09/02 10:30:55 nightmorph Exp $ -->
4
5 <guide link="/doc/en/gentoo-upgrading.xml">
6 <title>Gentoo Upgrading Guide</title>
7
8 <author title="Author">
9 <mail link="greg_g@gentoo.org">Gregorio Guidi</mail>
10 </author>
11 <author title="Editor">
12 <mail link="wolf31o2@gentoo.org">Chris Gianelloni</mail>
13 </author>
14
15 <abstract>
16 This document explains how new Gentoo releases affect existing installs.
17 </abstract>
18
19 <!-- The content of this document is licensed under the CC-BY-SA license -->
20 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
21 <license/>
22
23 <version>2.4</version>
24 <date>2006-09-02</date>
25
26 <chapter>
27 <title>Gentoo and Upgrades</title>
28 <section>
29 <title>Philosophy</title>
30 <body>
31
32 <p>
33 Here in Gentoo land, the concept of upgrading is quite different compared to
34 the rest of the Linux world. You probably already know that we never got in
35 touch with the "classic" way of upgrading software: waiting for a new release,
36 downloading it, burning, putting it in the cdrom drive and then following the
37 upgrade instructions.
38 </p>
39
40 <p>
41 You know (being a Gentoo user after all) that this process is extremely
42 frustrating for power users that want to live on the bleeding edge. Even power
43 users from other distributions probably share the same feelings, given the
44 popularity and spread of tools like apt or apt-rpm which make it
45 possible to have quick and frequent updates. However, no distribution is more
46 suited than Gentoo to satisfy these kind of demanding users. From the
47 beginning, Gentoo was designed around the concept of fast, incremental
48 updates.
49 </p>
50
51 <p>
52 Ideally, you install once and never bother with releases: just follow the
53 instructions in <uri
54 link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage
55 Introduction</uri> in the <uri link="/doc/en/handbook/">Gentoo Handbook</uri>
56 that explain how to keep your system up to date. While that's the way things
57 usually go, sometimes changes are made to the core system which require updates
58 to be done manually.
59 </p>
60
61 </body>
62 </section>
63 <section>
64 <title>Releases and Profiles</title>
65 <body>
66
67 <p>
68 A recurring question about the Gentoo release process is: "Why roll out new
69 releases frequently, if they are not intended to let users update software?".
70 There are various reasons:
71 </p>
72
73 <ul>
74 <li>
75 A new release means new Installation CDs with bugfixes and more features.
76 </li>
77 <li>
78 A new release provides an updated set of GRP packages, so that users that
79 choose "the fast way" to install (stage3 + precompiled packages) end up
80 with a system that is not outdated.
81 </li>
82 <li>
83 Finally, a new release may, from time to time, implement some features that
84 are incompatible with previous releases.
85 </li>
86 </ul>
87
88 <p>
89 When a release includes new incompatible features, or provides a set of core
90 packages and settings that deeply modify the behavior of the system, we say
91 that it provides a new <e>profile</e>.
92 </p>
93
94 <p>
95 A <e>profile</e> is a set of configuration files, stored in a subdirectory of
96 <path>/usr/portage/profiles</path>, that describe things such as the ebuilds
97 that are considered <e>system</e> packages, the default USE flags, the default
98 mapping for virtual packages, and the architecture on which the system is running.
99 </p>
100
101 <p>
102 The profile in use is determined by the symbolic link
103 <path>/etc/make.profile</path>, which points to a subdirectory of
104 <path>/usr/portage/profiles</path> which holds the profile files. For
105 instance, the default x86 2006.1 profile can be found
106 at <path>/usr/portage/profiles/default-linux/x86/2006.1</path>.
107 The files in the parent directories are part of the profile as well (and
108 are therefore shared by different subprofiles). This is why we call these
109 <e>cascaded profiles</e>.
110 </p>
111
112 <p>
113 Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path>
114 along with the current ones, but they are marked as deprecated. When that
115 happens a file named <path>deprecated</path> is put in the profile directory.
116 The content of this file is the name of the profile that should be "upgraded
117 to"; portage uses this information to automatically warn you when you should
118 update to a new profile.
119 </p>
120
121 <p>
122 There are various reasons that a new profile may be created: the release of
123 new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or
124 <c>glibc</c>) that are incompatible with previous versions, a change in
125 the default USE flags or in the virtual mappings, or maybe a change in
126 system-wide settings.
127 </p>
128
129 </body>
130 </section>
131 </chapter>
132
133 <chapter>
134 <title>Keeping up with new releases</title>
135 <section>
136 <title>Releases without profile changes</title>
137 <body>
138
139 <p>
140 If a new Gentoo release is announced that does not include a new profile
141 then you can safely pretend that it never happened :).
142 </p>
143
144 <p>
145 If you update your installed packages
146 <uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
147 the Gentoo Handbook</uri>, then your system will be exactly the same as one
148 that has been installed using the new release.
149 </p>
150
151 </body>
152 </section>
153 <section>
154 <title>Releases with profile changes</title>
155 <body>
156
157 <p>
158 If a release (such as 2006.1 for x86) introduces a new profile, you have the
159 choice to migrate to the new profile.
160 </p>
161
162 <p>
163 Naturally, you are not forced to do so, and you can continue to use the old
164 profile and just update your packages
165 <uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained
166 in the Gentoo Handbook</uri>.
167 </p>
168
169 <p>
170 However, Gentoo strongly recommends updating your profile if it becomes
171 deprecated. When this happens, it means that Gentoo developers no longer
172 plan on supporting it. Using the table below, you can quickly check to
173 see what profiles are currently supported.
174 </p>
175
176 <p>
177 If you decide to migrate to the new profile, then you will have to manually
178 perform the update. The way you update may vary significantly from release
179 to release; it depends on how deep the modifications introduced in the new
180 profile are.
181 </p>
182
183 <p>
184 In the simplest case you only have to change the <path>/etc/make.profile</path>
185 symlink, in the worst case you may have to recompile your system from scratch
186 while doing a neat voodoo dance. Migration is usually covered in the release
187 notes. You can also find <uri link="#instructions">instructions</uri> at the
188 end of this guide.
189 </p>
190
191 </body>
192 </section>
193 <section>
194 <title>Supported profiles</title>
195 <body>
196
197 <p>
198 The following profiles are officially supported by Gentoo developers:
199 </p>
200
201 <table>
202 <tr>
203 <th>Architecture</th>
204 <th>Most recent profiles</th>
205 <th>Other supported profiles</th>
206 </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>2006.0</ti>
276 <ti>2005.0, 2004.2</ti>
277 </tr>
278 <tr>
279 <th>s390</th>
280 <ti>2006.0</ti>
281 <ti>2004.3</ti>
282 </tr>
283 <tr>
284 <th>sparc</th>
285 <ti>
286 default-linux/sparc/sparc64/2006.1, default-linux/sparc/sparc64/2006.1/2.4
287 </ti>
288 <ti>
289 default-linux/sparc/sparc64/2006.0, default-linux/sparc/sparc64/2006.0/2.4
290 </ti>
291 </tr>
292 <tr>
293 <th>x86</th>
294 <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>
302 </tr>
303 </table>
304
305 </body>
306 </section>
307 </chapter>
308
309 <chapter id="instructions">
310 <title>Profile updating instructions</title>
311 <section>
312 <title>Updating to 2006.1</title>
313 <body>
314
315 <p>
316 To switch to the 2006.1 profile, point the <path>/etc/make.profile</path>
317 symlink to the new location. Make sure your Portage is updated before you
318 change 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>
327 Please 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>
329 sub-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>
339 To switch to the 2006.0 profile, point the <path>/etc/make.profile</path>
340 symlink to the new location. Make sure your Portage is updated before you
341 change 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
351 the default-linux/alpha/no-nptl profile. More information is available in <uri
352 link="/proj/en/releng/release/2006.0/alpha-release-notes.xml">the alpha release
353 notes</uri>.
354 </p>
355
356 <p>
357 <b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The ppc32
358 profile has been changed in a way that offers a minimalistic generic profile
359 for all purposes, located in default-linux/ppc/ppc32. The release-dependent
360 profile is optimized for desktop-usage and located in
361 default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and
362 G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop
363 Workstation. Make sure you choose the correct subprofile for your system when
364 migrating 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
369 requires manual user intervention (unmerging java stuff) and an <c>emerge -e
370 world</c> because of the <uri link="/doc/en/gcc-upgrading.xml">gcc
371 upgrade</uri>.<br/>
372 Upgrading to the <b>2.6</b>-kernel based 2006.0 profile which is not considered
373 stable also requires an entry in <path>/etc/portage/package.unmask</path> to
374 umask 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
379 specific 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>
389 To switch to the 2005.1 profile, point the <path>/etc/make.profile</path>
390 symlink to the new location. Make sure your Portage is updated before you
391 change 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
401 specific 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
406 and a number of subprofiles for specific subarchitectures were created. Make
407 sure you choose the correct subprofile for your system when migrating to a
408 2005.1 profile.
409 </p>
410
411 </body>
412 </section>
413 <section>
414 <title>Updating to 2005.0</title>
415 <body>
416
417 <p>
418 With the introduction of 2005.0, several architectures have decided to define
419 additional profiles. Make sure you read the description of said profiles before
420 you decide to migrate to one of them. Most architectures now also default to the
421 2.6 kernel tree where 2.4 was chosen previously.
422 </p>
423
424 <p>
425 Some architectures require a bit more actions to be completed in order to
426 convert from one profile to another. If that is the case, the step-by-step
427 guides 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>
550 To switch to the selected profile, point the <path>/etc/make.profile</path>
551 symlink to the new location. Make sure your Portage is updated before you change
552 your 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>
561 If you are running a Linux 2.4-based system but want to migrate to a 2.6-based
562 kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo
563 Linux 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>
573 With the introduction of the 2004.3 profiles, users are not going to see huge
574 modifications of their systems (see below for details). However, Gentoo
575 developers decided to push out this new profile and to deprecate quite a few of
576 the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the
577 profiles that follow the new layout of the <path>/usr/portage/profiles</path>
578 directory, for instance
579 <path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
580 Portage 2.0.51 or later).
581 </p>
582
583 <p>
584 To switch to the 2004.3 profile, point the <path>/etc/make.profile</path>
585 symlink to the new location:
586 </p>
587
588 <warn>
589 Don'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
600 profile. 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
602 that if you run <c>emerge --depclean</c>, Portage will try to remove them from
603 your system. If you need any of those packages, add them to
604 <path>/var/lib/portage/world</path> after the profile switch, or manually
605 emerge 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
611 effect 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>
621 Although this section does not seem to integrate well in this upgrading guide,
622 it is quite important. Any profile listed above this section requires a Portage
623 version that supports cascading profiles. However, some obsoleted profiles don't
624 allow the user to upgrade Portage or the user is using a profile that isn't
625 available anymore - any attempt to upgrade Portage will result in a failure.
626 </p>
627
628 <p>
629 To 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
631 they can continue with the upgrade procedure set forth in this guide. Please
632 substitute <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>
645 <title>Updating to 2004.2</title>
646 <body>
647
648 <p>
649 To switch to the 2004.2 profile, point the <path>/etc/make.profile</path>
650 symlink to the new location:
651 </p>
652
653 <warn>
654 Don't forget to upgrade Portage <e>before</e> you change your profile!!!
655 </warn>
656
657 <pre caption="Updating the /etc/make.profile symlink">
658 <comment>substitute &lt;arch&gt; with your arch</comment>
659 # <i>rm /etc/make.profile</i>
660 # <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i>
661 </pre>
662
663 <p>
664 <b>x86</b> - This profile changes the default X11 implementation from
665 <c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches
666 the <e>default</e> value, and is only relevant for those who have not installed
667 an X server yet. If you already have one installed, then it will not affect
668 you at all; you are free to switch from one X server to the other exactly as
669 before.
670 </p>
671
672 <p>
673 <b>amd64</b> - There are no fundamental changes from previous profiles, no
674 specific action needs to be performed.
675 </p>
676
677 </body>
678 </section>
679 <section>
680 <title>Updating to 2004.0</title>
681 <body>
682
683 <p>
684 To switch to the 2004.0 profile, point the <path>/etc/make.profile</path>
685 symlink to the new location:
686 </p>
687
688 <pre caption="Updating the /etc/make.profile symlink">
689 <comment>substitute &lt;arch&gt; with your arch</comment>
690 # <i>rm /etc/make.profile</i>
691 # <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/make.profile</i>
692 </pre>
693
694 <p>
695 <b>All archs</b> - There are no fundamental changes from previous profiles, no
696 specific action needs to be performed.
697 </p>
698
699 </body>
700 </section>
701 <section>
702 <title>Updating from profiles older than 1.4 to 1.4</title>
703 <body>
704
705 <p>
706 The instructions for this upgrade are quite complex, you can find them
707 <uri link="/doc/en/new-upgrade-to-gentoo-1.4.xml">here</uri>.
708 </p>
709
710 </body>
711 </section>
712 </chapter>
713
714 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20