/[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.45 - (show annotations) (download) (as text)
Sat Feb 9 08:46:08 2013 UTC (19 months, 3 weeks ago) by swift
Branch: MAIN
Changes since 1.44: +6 -6 lines
File MIME type: application/xml
Fix bug #453182 - Update profiles from 10.0 to 13.0

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.44 2012/10/31 18:17:54 swift Exp $ -->
4
5 <guide>
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 <author title="Editor">
15 <mail link="nightmorph@gentoo.org">Joshua Saddler</mail>
16 </author>
17
18 <abstract>
19 This document explains how new Gentoo releases affect existing installs.
20 </abstract>
21
22 <!-- The content of this document is licensed under the CC-BY-SA license -->
23 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
24 <license/>
25
26 <version>5</version>
27 <date>2013-02-09</date>
28
29 <chapter>
30 <title>Gentoo and Upgrades</title>
31 <section>
32 <title>Philosophy</title>
33 <body>
34
35 <p>
36 Here in Gentoo land, the concept of upgrading is quite different compared to
37 the rest of the Linux world. You probably already know that we never got in
38 touch with the "classic" way of upgrading software: waiting for a new release,
39 downloading it, burning, putting it in the cdrom drive and then following the
40 upgrade instructions.
41 </p>
42
43 <p>
44 You know (being a Gentoo user after all) that this process is extremely
45 frustrating for power users that want to live on the bleeding edge. Even power
46 users from other distributions probably share the same feelings, given the
47 popularity and spread of tools like apt or apt-rpm which make it
48 possible to have quick and frequent updates. However, no distribution is more
49 suited than Gentoo to satisfy these kind of demanding users. From the
50 beginning, Gentoo was designed around the concept of fast, incremental
51 updates.
52 </p>
53
54 <p>
55 Ideally, you install once and never bother with releases: just follow the
56 instructions in <uri
57 link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage
58 Introduction</uri> in the <uri link="/doc/en/handbook/">Gentoo Handbook</uri>
59 that explain how to keep your system up to date. While that's the way things
60 usually go, sometimes changes are made to the core system which require updates
61 to be done manually.
62 </p>
63
64 </body>
65 </section>
66 <section>
67 <title>Releases and Profiles</title>
68 <body>
69
70 <p>
71 A recurring question about the Gentoo release process is: "Why roll out new
72 releases frequently, if they are not intended to let users update software?"
73 There are various reasons:
74 </p>
75
76 <ul>
77 <li>
78 A new release means new Installation CDs with bugfixes and more features
79 </li>
80 <li>
81 A new release provides an updated set of GRP packages, so that users that
82 choose "the fast way" to install (stage3 + precompiled packages) end up
83 with a system that is not outdated
84 </li>
85 <li>
86 Finally, a new release may, from time to time, implement some features that
87 are incompatible with previous releases
88 </li>
89 </ul>
90
91 <p>
92 When a release includes new incompatible features, or provides a set of core
93 packages and settings that deeply modify the behavior of the system, we say
94 that it provides a new <e>profile</e>.
95 </p>
96
97 <p>
98 A <e>profile</e> is a set of configuration files, stored in a subdirectory of
99 <path>/usr/portage/profiles</path>, that describe things such as the ebuilds
100 that are considered <e>system</e> packages, the default USE flags, the default
101 mapping for virtual packages, and the architecture on which the system is running.
102 </p>
103
104 <p>
105 The profile in use is determined by the symbolic link
106 <path>/etc/portage/make.profile</path>, which points to a subdirectory of
107 <path>/usr/portage/profiles</path> which holds the profile files. For
108 instance, the default x86 13.0 profile can be found
109 at <path>/usr/portage/profiles/default/linux/x86/13.0</path>.
110 The files in the parent directories are part of the profile as well (and
111 are therefore shared by different subprofiles). This is why we call these
112 <e>cascaded profiles</e>.
113 </p>
114
115 <p>
116 Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path>
117 along with the current ones, but they are marked as deprecated. When that
118 happens a file named <path>deprecated</path> is put in the profile directory.
119 The content of this file is the name of the profile that should be "upgraded
120 to"; Portage uses this information to automatically warn you when you should
121 update to a new profile.
122 </p>
123
124 <p>
125 There are various reasons that a new profile may be created: the release of
126 new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or
127 <c>glibc</c>) that are incompatible with previous versions, a change in
128 the default USE flags or in the virtual mappings, or maybe a change in
129 system-wide settings.
130 </p>
131
132 </body>
133 </section>
134 </chapter>
135
136 <chapter>
137 <title>Keeping up with new releases</title>
138 <section>
139 <title>Releases without profile changes</title>
140 <body>
141
142 <p>
143 If a new Gentoo release does not include a new profile then you can safely
144 pretend that it never happened. :)
145 </p>
146
147 <p>
148 If you update your installed packages
149 <uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
150 the Gentoo Handbook</uri>, then your system will be exactly the same as one
151 that has been installed using the new release.
152 </p>
153
154 </body>
155 </section>
156 <section>
157 <title>Releases with profile changes</title>
158 <body>
159
160 <p>
161 If a release (such as 13.0 for x86) introduces a new profile, you have the
162 choice to migrate to the new profile.
163 </p>
164
165 <p>
166 Naturally, you are not forced to do so, and you can continue to use the old
167 profile and just update your packages
168 <uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained
169 in the Gentoo Handbook</uri>.
170 </p>
171
172 <p>
173 However, Gentoo strongly recommends updating your profile if it becomes
174 deprecated. When this happens, it means that Gentoo developers no longer
175 plan on supporting it.
176 </p>
177
178 <p>
179 If you decide to migrate to the new profile, then you will have to manually
180 perform the update. The way you update may vary significantly from release
181 to release; it depends on how deep the modifications introduced in the new
182 profile are.
183 </p>
184
185 <p>
186 In the simplest case you only have to change the <path>/etc/portage/make.profile</path>
187 symlink, in the worst case you may have to recompile your system from scratch
188 while doing a neat voodoo dance. Migration is usually covered in the release
189 notes. You can also find <uri link="#instructions">instructions</uri> at the
190 end of this guide.
191 </p>
192
193 </body>
194 </section>
195 <section>
196 <title>Supported profiles</title>
197 <body>
198
199 <p>
200 You can view the list of profiles on your architecture officially supported by
201 Gentoo developers when you <c>emerge eselect</c> and then run the following
202 command:
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>
220 Make sure your Portage is updated before performing any profile changes.
221 </impo>
222
223 <p>
224 First, run <c>emerge eselect</c>. The <c>eselect</c> utility will let you view
225 and select profiles easily, without needing to create or remove symlinks by
226 hand.
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>
238 If 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>
248 There are <b>desktop</b> and <b>server</b> subprofiles for most architectures.
249 Examine these profiles carefully, as they may serve your needs better than the
250 extremely minimal default profiles.
251 </note>
252
253 <note>
254 The <c>developer</c> subprofile is specifically for Gentoo Linux development
255 tasks. 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>
265 If you intend to upgrade to these profiles, you should be aware that they expect
266 the system to be set to a Unicode locale by default; specifically that
267 UNICODE="yes" is set in <path>/etc/rc.conf</path>. For this to work, you must
268 have created a Unicode locale for your system to use. Please read our <uri
269 link="/doc/en/utf-8.xml">UTF-8 guide</uri> to learn how to create the proper
270 locale.
271 </p>
272
273 <p>
274 Alternatively, if you do not wish to set a locale, you should specify
275 UNICODE="no" in <path>/etc/rc.conf</path>, and re-emerge <c>baselayout</c> (or
276 wait until your next <c>baselayout</c> update) with the <c>-unicode</c> USE
277 flag. You can set <c>-unicode</c> just for <c>baselayout</c>, or you can set it
278 globally 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>
289 USE="-unicode"
290 # <i>emerge -a baselayout</i>
291 </pre>
292
293 <note>
294 If you are updating to a 2007.0 profile on the Sparc architecture, then you will
295 need to follow the <uri link="/doc/en/gcc-upgrading.xml">GCC Upgrading
296 Guide</uri>, as <c>gcc-4</c> is the default compiler.
297 </note>
298
299 <p>
300 Finally, follow the <uri link="#general">general instructions</uri> for updating
301 your profile.
302 </p>
303
304 </body>
305 </section>
306 <section>
307 <title>Updating to 2006.0</title>
308 <body>
309
310 <p>
311 To switch to the 2006.0 profile, point the <path>/etc/portage/make.profile</path>
312 symlink to the new location. Make sure your Portage is updated before you
313 change 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
323 the default-linux/alpha/no-nptl profile. More information is available in <uri
324 link="/proj/en/releng/release/2006.0/alpha-release-notes.xml">the alpha release
325 notes</uri>.
326 </p>
327
328 <p>
329 <b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The ppc32
330 profile has been changed in a way that offers a minimalistic generic profile
331 for all purposes, located in default-linux/ppc/ppc32. The release-dependent
332 profile is optimized for desktop-usage and located in
333 default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and
334 G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop
335 Workstation. Make sure you choose the correct subprofile for your system when
336 migrating 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
341 requires manual user intervention (unmerging java stuff) and an <c>emerge -e
342 world</c> because of the <uri link="/doc/en/gcc-upgrading.xml">gcc
343 upgrade</uri>.<br/>
344 Upgrading to the <b>2.6</b>-kernel based 2006.0 profile which is not considered
345 stable also requires an entry in <path>/etc/portage/package.unmask</path> to
346 umask 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
351 specific 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>
361 To switch to the 2005.1 profile, point the <path>/etc/portage/make.profile</path>
362 symlink to the new location. Make sure your Portage is updated before you
363 change 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
373 specific 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
378 and a number of subprofiles for specific subarchitectures were created. Make
379 sure you choose the correct subprofile for your system when migrating to a
380 2005.1 profile.
381 </p>
382
383 </body>
384 </section>
385 <section>
386 <title>Updating to 2005.0</title>
387 <body>
388
389 <p>
390 With the introduction of 2005.0, several architectures have decided to define
391 additional profiles. Make sure you read the description of said profiles before
392 you decide to migrate to one of them. Most architectures now also default to the
393 2.6 kernel tree where 2.4 was chosen previously.
394 </p>
395
396 <p>
397 Some architectures require a bit more actions to be completed in order to
398 convert from one profile to another. If that is the case, the step-by-step
399 guides are linked from the table.
400 </p>
401
402 <table>
403 <tr>
404 <th>Profile</th>
405 <th>Description</th>
406 <th>Specific Upgrade Guide</th>
407 </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>
412 </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>
417 </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>
422 </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>
427 </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>
432 </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>
437 </tr>
438 <tr>
439 <ti>default-linux/hppa/2005.0/2.4</ti>
440 <ti>HPPA 2005.0 profile for 2.4 kernels</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>
517 <ti></ti>
518 </tr>
519 </table>
520
521 <p>
522 To switch to the selected profile, point the <path>/etc/portage/make.profile</path>
523 symlink to the new location. Make sure your Portage is updated before you change
524 your profile!
525 </p>
526
527 <pre caption="Changing to a 2005.0 profile">
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>
533 If you are running a Linux 2.4-based system but want to migrate to a 2.6-based
534 kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo
535 Linux 2.6 Migration Guide</uri>.
536 </p>
537
538 </body>
539 </section>
540 <section>
541 <title>Updating to 2004.3</title>
542 <body>
543
544 <p>
545 With the introduction of the 2004.3 profiles, users are not going to see huge
546 modifications of their systems (see below for details). However, Gentoo
547 developers decided to push out this new profile and to deprecate quite a few of
548 the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the
549 profiles that follow the new layout of the <path>/usr/portage/profiles</path>
550 directory, for instance
551 <path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
552 Portage 2.0.51 or later).
553 </p>
554
555 <p>
556 To switch to the 2004.3 profile, point the <path>/etc/portage/make.profile</path>
557 symlink to the new location:
558 </p>
559
560 <warn>
561 Don'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
572 profile. 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
574 that if you run <c>emerge --depclean</c>, Portage will try to remove them from
575 your system. If you need any of those packages, add them to
576 <path>/var/lib/portage/world</path> after the profile switch, or manually
577 emerge 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
583 effect on already installed machines, though.
584 </p>
585
586 </body>
587 </section>
588 <section>
589 <title>Updating Portage to Support Cascading Profiles</title>
590 <body>
591
592 <p>
593 Although this section does not seem to integrate well in this upgrading guide,
594 it is quite important. Any profile listed above this section requires a Portage
595 version that supports cascading profiles. However, some obsoleted profiles don't
596 allow the user to upgrade Portage or the user is using a profile that isn't
597 available anymore - any attempt to upgrade Portage will result in a failure.
598 </p>
599
600 <p>
601 To 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
603 they can continue with the upgrade procedure set forth in this guide. Please
604 substitute <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>
621 To switch to the 2004.2 profile, point the <path>/etc/portage/make.profile</path>
622 symlink to the new location:
623 </p>
624
625 <warn>
626 Don't forget to upgrade Portage <e>before</e> you change your profile!!!
627 </warn>
628
629 <pre caption="Updating the /etc/portage/make.profile symlink">
630 <comment>substitute &lt;arch&gt; with your arch</comment>
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
638 the <e>default</e> value, and is only relevant for those who have not installed
639 an X server yet. If you already have one installed, then it will not affect
640 you at all; you are free to switch from one X server to the other exactly as
641 before.
642 </p>
643
644 <p>
645 <b>amd64</b> - There are no fundamental changes from previous profiles, no
646 specific 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>
656 To switch to the 2004.0 profile, point the <path>/etc/portage/make.profile</path>
657 symlink 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>
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
668 specific action needs to be performed.
669 </p>
670
671 </body>
672 </section>
673 <section>
674 <title>Updating from profiles older than 1.4 to 1.4</title>
675 <body>
676
677 <p>
678 The instructions for this upgrade are quite complex, you can find them
679 <uri link="/doc/en/new-upgrade-to-gentoo-1.4.xml">here</uri>.
680 </p>
681
682 </body>
683 </section>
684 </chapter>
685
686 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20