/[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.13 Revision 1.14
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.13 2004/11/08 10:00:49 swift Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.14 2004/11/08 10:03:14 swift 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="g.guidi@sns.it">Gregorio Guidi</mail>
10</author> 10</author>
11 11
12<abstract> 12<abstract>
13This document explains how new Gentoo releases affect existing installs. 13This document explains how new Gentoo releases affect existing installs.
14</abstract> 14</abstract>
15 15
16<!-- The content of this document is licensed under the CC-BY-SA license --> 16<!-- The content of this document is licensed under the CC-BY-SA license -->
17<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> 17<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
18<license/> 18<license/>
19 19
20<version>2.5</version> 20<version>2.6</version>
21<date>November 08, 2004</date> 21<date>November 08, 2004</date>
22 22
23<chapter> 23<chapter>
24<title>Gentoo and Upgrades</title> 24<title>Gentoo and Upgrades</title>
25<section> 25<section>
26<title>Philosophy</title> 26<title>Philosophy</title>
27<body> 27<body>
28 28
29<p> 29<p>
30Here in Gentoo land, the concept of upgrading is quite different compared to 30Here in Gentoo land, the concept of upgrading is quite different compared to
31the rest of the Linux world. You probably already know that we never got in 31the rest of the Linux world. You probably already know that we never got in
32touch with the "classic" way of upgrading software: waiting for a new release, 32touch with the "classic" way of upgrading software: waiting for a new release,
33downloading it, burning, putting it in the cdrom drive and then following the 33downloading it, burning, putting it in the cdrom drive and then following the
34upgrade instructions. 34upgrade instructions.
35</p> 35</p>
93that are considered <e>system</e> packages, the default USE flags, the default 93that are considered <e>system</e> packages, the default USE flags, the default
94mapping for virtual packages, and the architecture on which the system is running. 94mapping for virtual packages, and the architecture on which the system is running.
95</p> 95</p>
96 96
97<p> 97<p>
98The profile in use is determined by the symbolic link 98The profile in use is determined by the symbolic link
99<path>/etc/make.profile</path>, which points to a subdirectory of 99<path>/etc/make.profile</path>, which points to a subdirectory of
100<path>/usr/portage/profiles</path> which holds the profile files. For instance, 100<path>/usr/portage/profiles</path> which holds the profile files. For instance,
101the x86 2004.2 profile can be found at <path>/usr/portage/profiles/default-x86-2004.2</path> 101the x86 2004.2 profile can be found at <path>/usr/portage/profiles/default-x86-2004.2</path>
102(old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style 102(old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style
103location - only for use with Portage 2.0.51 and later). With respect to new-style profile directories, note that the files in 103location - only for use with Portage 2.0.51 and later). With respect to new-style profile directories, note that the files in
104parent directories are part of the profile (and are therefore shared 104parent directories are part of the profile (and are therefore shared
105by different subprofiles). 105by different subprofiles).
106</p> 106</p>
107 107
108<warn>
109To use the new-style profiles called <e>cascading profiles</e> you first need to
110upgrade Portage and then change the profile symlink.
111</warn>
112
113<p> 108<p>
114Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> 109Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path>
115along with the current ones, but they are marked as deprecated. When that happens a 110along with the current ones, but they are marked as deprecated. When that happens a
116file named <path>deprecated</path> is put in the profile directory. The content 111file named <path>deprecated</path> is put in the profile directory. The content
117of this file is the name of the profile that should be "upgraded to"; portage uses 112of this file is the name of the profile that should be "upgraded to"; portage uses
118this information to automatically warn you when you should update to a new profile. 113this information to automatically warn you when you should update to a new profile.
119</p> 114</p>
120 115
121<p> 116<p>
122There are various reasons that a new profile may be created: the release of new 117There are various reasons that a new profile may be created: the release of new
123versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or <c>glibc</c>) 118versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or <c>glibc</c>)
124that are incompatible with previous versions, a change in the default USE flags or 119that are incompatible with previous versions, a change in the default USE flags or
125in the virtual mappings, or maybe a change in system-wide settings (such as defining 120in the virtual mappings, or maybe a change in system-wide settings (such as defining
126udev to be the default manager for <path>/dev</path> instead of devfs). 121udev to be the default manager for <path>/dev</path> instead of devfs).
127</p> 122</p>
271With the introduction of the 2004.3 profiles, users are not going to see huge 266With the introduction of the 2004.3 profiles, users are not going to see huge
272modifications of their systems (see below for details). However, Gentoo 267modifications of their systems (see below for details). However, Gentoo
273developers decided to push out this new profile and to deprecate quite a few of 268developers decided to push out this new profile and to deprecate quite a few of
274the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the 269the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the
275profiles that follow the new layout of the <path>/usr/portage/profiles</path> 270profiles that follow the new layout of the <path>/usr/portage/profiles</path>
276directory, for instance 271directory, for instance
277<path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by 272<path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
278Portage 2.0.51 or later). 273Portage 2.0.51 or later).
279</p> 274</p>
280 275
281<p> 276<p>
282To switch to the 2004.3 profile, point the <path>/etc/make.profile</path> 277To switch to the 2004.3 profile, point the <path>/etc/make.profile</path>
283symlink to the new location: 278symlink to the new location:
284</p> 279</p>
285 280
281<warn>
282Don't forget to upgrade Portage <e>before</e> you change your profile!!!
283</warn>
284
285
286<pre caption="Updating the /etc/make.profile symlink"> 286<pre caption="Updating the /etc/make.profile symlink">
287<comment>substitute &lt;arch&gt; with your arch</comment> 287<comment>substitute &lt;arch&gt; with your arch</comment>
288# <i>rm /etc/make.profile</i> 288# <i>rm /etc/make.profile</i>
289# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i> 289# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i>
290</pre> 290</pre>
291 291
292<p> 292<p>
293<b>All archs</b> - As said above, there are no big changes introduced in this 293<b>All archs</b> - As said above, there are no big changes introduced in this
294profile. However, it should be noted that <c>sys-apps/slocate</c> and 294profile. However, it should be noted that <c>sys-apps/slocate</c> and
295<c>net-misc/dhcpcd</c> are no longer considered system packages. This means 295<c>net-misc/dhcpcd</c> are no longer considered system packages. This means
296that if you run <c>emerge depclean</c>, Portage will try to remove them from 296that if you run <c>emerge depclean</c>, Portage will try to remove them from
297your system. If you need any of those packages, add them to 297your system. If you need any of those packages, add them to
298<path>/var/lib/portage/world</path> after the profile switch, or manually 298<path>/var/lib/portage/world</path> after the profile switch, or manually
299emerge them. 299emerge them.
300</p> 300</p>

Legend:
Removed from v.1.13  
changed lines
  Added in v.1.14

  ViewVC Help
Powered by ViewVC 1.1.20