/[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.18 Revision 1.19
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.18 2005/01/25 11:48:14 neysx Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.19 2005/01/25 21:37:58 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="greg_g@gentoo.org">Gregorio Guidi</mail> 9 <mail link="greg_g@gentoo.org">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/>
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>
36 36
37<p> 37<p>
38You know (being a Gentoo user after all) that this process is extremely 38You 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 39frustrating for power users that want to live on the bleeding edge. Even power
40users from other distributions probably share the same feelings, given the 40users from other distributions probably share the same feelings, given the
41popularity and spread of tools like apt or apt-rpm which make it 41popularity and spread of tools like apt or apt-rpm which make it
42possible to have quick and frequent updates. However, no distibution is more 42possible to have quick and frequent updates. However, no distibution is more
43suited than Gentoo to satisfy these kind of demanding users. From the beginning, 43suited than Gentoo to satisfy these kind of demanding users. From the
44Gentoo was designed around the concept of fast, incremental updates. 44beginning, Gentoo was designed around the concept of fast, incremental
45updates.
45</p> 46</p>
46 47
47<p> 48<p>
48Ideally, you install once and never bother with releases: just follow the 49Ideally, you install once and never bother with releases: just follow the
49instructions in <uri 50instructions in <uri
50link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage 51link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage
51Introduction</uri> in the <uri link="/doc/en/handbook/">Gentoo Handbook</uri> 52Introduction</uri> in the <uri link="/doc/en/handbook/">Gentoo Handbook</uri>
52that explain how to keep your system up to date. While that's the way things 53that explain how to keep your system up to date. While that's the way things
53usually go, sometimes changes are made to the core system which require updates 54usually go, sometimes changes are made to the core system which require updates
54to be done manually. 55to be done manually.
55</p> 56</p>
56 57
57</body> 58</body>
58</section> 59</section>
59<section> 60<section>
85When a release includes new incompatible features, or provides a set of core 86When a release includes new incompatible features, or provides a set of core
86packages and settings that deeply modify the behavior of the system, we say 87packages and settings that deeply modify the behavior of the system, we say
87that it provides a new <e>profile</e>. 88that it provides a new <e>profile</e>.
88</p> 89</p>
89 90
90<p> 91<p>
91A <e>profile</e> is a set of configuration files, stored in a subdirectory of 92A <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 93<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 94that 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. 95mapping for virtual packages, and the architecture on which the system is running.
95</p> 96</p>
96 97
97<p> 98<p>
98The profile in use is determined by the symbolic link 99The profile in use is determined by the symbolic link
99<path>/etc/make.profile</path>, which points to a subdirectory of 100<path>/etc/make.profile</path>, which points to a subdirectory of
100<path>/usr/portage/profiles</path> which holds the profile files. For instance, 101<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> 102instance, the x86 2004.2 profile can be found at
103<path>/usr/portage/profiles/default-x86-2004.2</path> (old-style location) or
102(old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style 104at <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 105location - only for use with Portage 2.0.51 and later). With respect to
106new-style profile directories, note that the files in
104parent directories are part of the profile (and are therefore shared 107parent directories are part of the profile (and are therefore shared
105by different subprofiles). 108by different subprofiles).
106</p> 109</p>
107 110
108<p> 111<p>
109Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> 112Profiles 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 113along 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 114happens 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 115The 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. 116to"; portage uses this information to automatically warn you when you should
114</p> 117update to a new profile.
115
116<p> 118</p>
119
120<p>
117There are various reasons that a new profile may be created: the release of new 121There 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>) 122new 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 123<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 124the 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). 125system-wide settings (such as defining udev to be the default manager
126for <path>/dev</path> instead of devfs).
122</p> 127</p>
123 128
124</body> 129</body>
125</section> 130</section>
126</chapter> 131</chapter>
127 132
128<chapter> 133<chapter>
129<title>Keeping up with new releases</title> 134<title>Keeping up with new releases</title>
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 (such
136as the 2004.1 release for x86), then you can safely pretend that it never 141as the 2004.1 release for x86), then you can safely pretend that it never
144that has been installed using the new release. 149that has been installed using the new release.
145</p> 150</p>
146 151
147</body> 152</body>
148</section> 153</section>
149<section> 154<section>
150<title>Releases with profile changes</title> 155<title>Releases with profile changes</title>
151<body> 156<body>
152 157
153<p> 158<p>
154If a release introduces a new profile, you have the choice to migrate to the 159If a release introduces a new profile, you have the choice to migrate to the
155new profile. 160new profile.
156</p> 161</p>
157 162
158<p> 163<p>
159Naturally, you are not forced to do so, and you can continue to use the old profile 164Naturally, you are not forced to do so, and you can continue to use the old
160and just update your packages 165profile and just update your packages
161<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in 166<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained
162the Gentoo Handbook</uri>. 167in the Gentoo Handbook</uri>.
163</p>
164
165<p> 168</p>
169
170<p>
166However, Gentoo strongly recommends updating your profile if it becomes deprecated. 171However, Gentoo strongly recommends updating your profile if it becomes
167When this happens, it means that Gentoo developers no longer plan on supporting it. 172deprecated. 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. 173plan on supporting it. Using the table below, you can quickly check to
174see what profiles are currently supported.
169</p> 175</p>
170 176
171<p> 177<p>
172If you decide to migrate to the new profile, then you will have to manually 178If 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 179perform the update. The way you update may vary significantly from release
174depends on how deep the modifications introduced in the new profile are. 180to release; it depends on how deep the modifications introduced in the new
181profile are.
175</p> 182</p>
176 183
177<p> 184<p>
178In the simplest case you only have to change the <path>/etc/make.profile</path> 185In 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 186symlink, in the worst case you may have to recompile your system from scratch
180while doing a neat voodoo dance. Migration is usually covered in the release 187while doing a neat voodoo dance. Migration is usually covered in the release
181notes (e.g. <uri 188notes (e.g. <uri
182link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3 189link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3
183release notes</uri>). You can also find <uri 190release notes</uri>). You can also find <uri
184link="#instructions">instructions</uri> at the end of this guide. 191link="#instructions">instructions</uri> at the end of this guide.
185</p> 192</p>
186 193
187</body> 194</body>
188</section> 195</section>
189<section> 196<section>
190<title>Supported profiles</title> 197<title>Supported profiles</title>
191<body> 198<body>
192 199
193<p> 200<p>
194The following profiles are officially supported by Gentoo developers: 201The following profiles are officially supported by Gentoo developers:
195</p> 202</p>
196 203
287# <i>rm /etc/make.profile</i> 294# <i>rm /etc/make.profile</i>
288# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i> 295# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i>
289</pre> 296</pre>
290 297
291<p> 298<p>
292<b>All archs</b> - As said above, there are no big changes introduced in this 299<b>All archs</b> - As said above, there are no big changes introduced in this
293profile. However, it should be noted that <c>sys-apps/slocate</c> and 300profile. However, it should be noted that <c>sys-apps/slocate</c> and
294<c>net-misc/dhcpcd</c> are no longer considered system packages. This means 301<c>net-misc/dhcpcd</c> are no longer considered system packages. This means
295that if you run <c>emerge --depclean</c>, Portage will try to remove them from 302that if you run <c>emerge --depclean</c>, Portage will try to remove them from
296your system. If you need any of those packages, add them to 303your system. If you need any of those packages, add them to
297<path>/var/lib/portage/world</path> after the profile switch, or manually 304<path>/var/lib/portage/world</path> after the profile switch, or manually
298emerge them. 305emerge them.
299</p> 306</p>
300 307
301<p> 308<p>
302<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/devfs</c> 309<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of
303for newly installed machines. This has no effect on already installed machines, 310<c>sys-fs/devfs</c> for newly installed machines. This has no
304though. 311effect on already installed machines, though.
305</p> 312</p>
306 313
307</body> 314</body>
308</section> 315</section>
309<section> 316<section>
310<title>Updating to 2004.2</title> 317<title>Updating to 2004.2</title>
311<body> 318<body>
312 319
313<p> 320<p>
314To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink 321To switch to the 2004.2 profile, point the <path>/etc/make.profile</path>
315to the new location: 322symlink to the new location:
316</p> 323</p>
317 324
318<warn> 325<warn>
319Don't forget to upgrade Portage <e>before</e> you change your profile!!! 326Don't forget to upgrade Portage <e>before</e> you change your profile!!!
320</warn> 327</warn>
321 328
322<pre caption="Updating the /etc/make.profile symlink"> 329<pre caption="Updating the /etc/make.profile symlink">
323<comment>substitute &lt;arch&gt; with your arch</comment> 330<comment>substitute &lt;arch&gt; with your arch</comment>
324# <i>rm /etc/make.profile</i> 331# <i>rm /etc/make.profile</i>
325# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i> 332# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i>
326</pre> 333</pre>
327 334
328<p> 335<p>
329<b>x86</b> - This profile changes the default X11 implementation from 336<b>x86</b> - This profile changes the default X11 implementation from
330<c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches 337<c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches
334before. 341before.
335</p> 342</p>
336 343
337<p> 344<p>
338<b>amd64</b> - There are no fundamental changes from previous profiles, no 345<b>amd64</b> - There are no fundamental changes from previous profiles, no
339specific action needs to be performed. 346specific action needs to be performed.
340</p> 347</p>
341 348
342</body> 349</body>
343</section> 350</section>
344<section> 351<section>
345<title>Updating to 2004.0</title> 352<title>Updating to 2004.0</title>
346<body> 353<body>
347 354
348<p> 355<p>
349To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> symlink 356To switch to the 2004.0 profile, point the <path>/etc/make.profile</path>
350to the new location: 357symlink to the new location:
351</p> 358</p>
352 359
353<pre caption="Updating the /etc/make.profile symlink"> 360<pre caption="Updating the /etc/make.profile symlink">
354<comment>substitute &lt;arch&gt; with your arch</comment> 361<comment>substitute &lt;arch&gt; with your arch</comment>
355# <i>rm /etc/make.profile</i> 362# <i>rm /etc/make.profile</i>
356# <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/make.profile</i> 363# <i>ln -s ../usr/portage/profiles/default-&lt;arch&gt;-2004.0 /etc/make.profile</i>
357</pre> 364</pre>
358 365
359<p> 366<p>
360<b>All archs</b> - There are no fundamental changes from previous profiles, no 367<b>All archs</b> - There are no fundamental changes from previous profiles, no
361specific action needs to be performed. 368specific action needs to be performed.
362</p> 369</p>
363 370
364</body> 371</body>
365</section> 372</section>

Legend:
Removed from v.1.18  
changed lines
  Added in v.1.19

  ViewVC Help
Powered by ViewVC 1.1.20