/[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.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.11 2004/10/24 22:48:37 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="g.guidi@sns.it">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/1.0 --> 17<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
18<license/> 18<license/>
19 19
20<version>2.3</version> 20<version>2.8</version>
21<date>September 25, 2004</date> 21<date>2005-01-22</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>
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
45</p> 45updates.
46
47<p> 46</p>
47
48<p>
48Ideally, you install once and then do not to bother with releases: 49Ideally, you install once and never bother with releases: just follow the
49just follow the instructions in 50instructions in <uri
50<uri link="/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 52Introduction</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 53that 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 54usually 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. 55to be done manually.
55</p> 56</p>
56 57
57</body> 58</body>
58</section> 59</section>
59<section> 60<section>
70 <li> 71 <li>
71 A new release means new LiveCDs with bugfixes and more features. 72 A new release means new LiveCDs with bugfixes and more features.
72 </li> 73 </li>
73 <li> 74 <li>
74 A new release provides an updated set of GRP packages, so that users that 75 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 76 choose "the fast way" to install (stage3 + precompiled packages) end up
76 with a system that is not outdated. 77 with a system that is not outdated.
77 </li> 78 </li>
78 <li> 79 <li>
79 Finally, a new release may, from time to time, implement some features that 80 Finally, a new release may, from time to time, implement some features that
80 are incompatible with previous releases. 81 are incompatible with previous releases.
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 architecture that 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>
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. 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. Regardless, we will publish migration instructions 187while 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. 188notes (e.g. <uri
189link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3
190release notes</uri>). You can also find <uri
191link="#instructions">instructions</uri> at the end of this guide.
182</p> 192</p>
183 193
184</body> 194</body>
185</section> 195</section>
186<section> 196<section>
196 <th>Architecture</th> 206 <th>Architecture</th>
197 <th>Most recent profile</th> 207 <th>Most recent profile</th>
198 <th>Other supported profiles</th> 208 <th>Other supported profiles</th>
199</tr> 209</tr>
200<tr> 210<tr>
211 <th>alpha</th>
212 <ti>2004.3</ti>
213 <ti></ti>
214</tr>
215<tr>
201 <th>arm</th> 216 <th>arm</th>
217 <ti>2004.3</ti>
218 <ti></ti>
219</tr>
220<tr>
221 <th>amd64</th>
222 <ti>2004.3</ti>
223 <ti>2004.2, 2004.0</ti>
224</tr>
225<tr>
226 <th>hppa</th>
227 <ti>2004.3</ti>
228 <ti>2004.2</ti>
229</tr>
230<tr>
231 <th>ia64</th>
232 <ti>2004.3</ti>
233 <ti></ti>
234</tr>
235<tr>
236 <th>ppc</th>
237 <ti>2004.3</ti>
202 <ti>2004.0</ti> 238 <ti>2004.0</ti>
203 <ti></ti>
204</tr>
205<tr> 239</tr>
240<tr>
206 <th>amd64</th> 241 <th>mips</th>
207 <ti>2004.2</ti> 242 <ti>2004.2</ti>
243 <ti></ti>
244</tr>
245<tr>
246 <th>s390</th>
247 <ti>2004.3</ti>
248 <ti></ti>
249</tr>
250<tr>
251 <th>sparc</th>
252 <ti>2004.3</ti>
208 <ti>2004.0</ti> 253 <ti>2004.0</ti>
209</tr> 254</tr>
210<tr> 255<tr>
211 <th>hardened-x86</th>
212 <ti>2004.0</ti>
213 <ti></ti>
214</tr>
215<tr>
216 <th>hppa</th>
217 <ti>2004.0</ti>
218 <ti></ti>
219</tr>
220<tr>
221 <th>ppc</th>
222 <ti>2004.0</ti>
223 <ti></ti>
224</tr>
225<tr>
226 <th>mips</th>
227 <ti>2004.1</ti>
228 <ti>1.4</ti>
229</tr>
230<tr>
231 <th>sparc</th>
232 <ti>2004.0</ti>
233 <ti></ti>
234</tr>
235<tr>
236 <th>sparc64</th>
237 <ti>2004.0</ti>
238 <ti></ti>
239</tr>
240<tr>
241 <th>x86</th> 256 <th>x86</th>
242 <ti>2004.2</ti> 257 <ti>2004.3</ti>
243 <ti>2004.0, 1.4</ti> 258 <ti>2004.2, 2004.0</ti>
244</tr> 259</tr>
245</table> 260</table>
246 261
247</body> 262</body>
248</section> 263</section>
249</chapter> 264</chapter>
250 265
251<chapter> 266<chapter id="instructions">
252<title>Profile updating instructions</title> 267<title>Profile updating instructions</title>
253<section> 268<section>
269<title>Updating to 2004.3</title>
270<body>
271
272<p>
273With the introduction of the 2004.3 profiles, users are not going to see huge
274modifications of their systems (see below for details). However, Gentoo
275developers decided to push out this new profile and to deprecate quite a few of
276the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the
277profiles that follow the new layout of the <path>/usr/portage/profiles</path>
278directory, for instance
279<path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
280Portage 2.0.51 or later).
281</p>
282
283<p>
284To switch to the 2004.3 profile, point the <path>/etc/make.profile</path>
285symlink to the new location:
286</p>
287
288<warn>
289Don't forget to upgrade Portage <e>before</e> you change your profile!!!
290</warn>
291
292<pre caption="Updating the /etc/make.profile symlink">
293<comment>substitute &lt;arch&gt; with your arch</comment>
294# <i>rm /etc/make.profile</i>
295# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i>
296</pre>
297
298<p>
299<b>All archs</b> - As said above, there are no big changes introduced in this
300profile. However, it should be noted that <c>sys-apps/slocate</c> and
301<c>net-misc/dhcpcd</c> are no longer considered system packages. This means
302that if you run <c>emerge --depclean</c>, Portage will try to remove them from
303your system. If you need any of those packages, add them to
304<path>/var/lib/portage/world</path> after the profile switch, or manually
305emerge them.
306</p>
307
308<p>
309<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of
310<c>sys-fs/devfs</c> for newly installed machines. This has no
311effect on already installed machines, though.
312</p>
313
314</body>
315</section>
316<section>
254<title>Updating to 2004.2</title> 317<title>Updating to 2004.2</title>
255<body> 318<body>
256 319
257<p> 320<p>
258To 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>
259to the new location: 322symlink to the new location:
260</p> 323</p>
324
325<warn>
326Don't forget to upgrade Portage <e>before</e> you change your profile!!!
327</warn>
261 328
262<pre caption="Updating the /etc/make.profile symlink"> 329<pre caption="Updating the /etc/make.profile symlink">
263<comment>substitute &lt;arch&gt; with your arch</comment> 330<comment>substitute &lt;arch&gt; with your arch</comment>
264# <i>rm /etc/make.profile</i> 331# <i>rm /etc/make.profile</i>
265# <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>
284<section> 351<section>
285<title>Updating to 2004.0</title> 352<title>Updating to 2004.0</title>
286<body> 353<body>
287 354
288<p> 355<p>
289To 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>
290to the new location: 357symlink to the new location:
291</p> 358</p>
292 359
293<pre caption="Updating the /etc/make.profile symlink"> 360<pre caption="Updating the /etc/make.profile symlink">
294<comment>substitute &lt;arch&gt; with your arch</comment> 361<comment>substitute &lt;arch&gt; with your arch</comment>
295# <i>rm /etc/make.profile</i> 362# <i>rm /etc/make.profile</i>

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

  ViewVC Help
Powered by ViewVC 1.1.20