/[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.23 Revision 1.24
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.23 2005/06/27 00:27:17 vanquirius Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.24 2005/08/12 10:29:12 neysx 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.5 -->
18<license/> 18<license/>
19 19
20<version>2.12</version> 20<version>2.13</version>
21<date>2005-06-27</date> 21<date>2005-08-12</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>
36 36
87packages 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
88that it provides a new <e>profile</e>. 88that it provides a new <e>profile</e>.
89</p> 89</p>
90 90
91<p> 91<p>
92A <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
93<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
94that 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
95mapping 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.
96</p> 96</p>
97 97
98<p> 98<p>
99The profile in use is determined by the symbolic link 99The profile in use is determined by the symbolic link
100<path>/etc/make.profile</path>, which points to a subdirectory of 100<path>/etc/make.profile</path>, which points to a subdirectory of
101<path>/usr/portage/profiles</path> which holds the profile files. For 101<path>/usr/portage/profiles</path> which holds the profile files. For
102instance, the default x86 2005.0 profile can be found 102instance, the default x86 2005.1 profile can be found
103at <path>/usr/portage/profiles/default-linux/x86/2005.0</path>. 103at <path>/usr/portage/profiles/default-linux/x86/2005.1</path>.
104The files in the parent directories are part of the profile as well (and 104The files in the parent directories are part of the profile as well (and
105are therefore shared by different subprofiles). This is why we call these 105are therefore shared by different subprofiles). This is why we call these
106<e>cascaded profiles</e>. 106<e>cascaded profiles</e>.
107</p> 107</p>
108 108
109<p> 109<p>
110Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> 110Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path>
111along with the current ones, but they are marked as deprecated. When that 111along with the current ones, but they are marked as deprecated. When that
112happens a file named <path>deprecated</path> is put in the profile directory. 112happens a file named <path>deprecated</path> is put in the profile directory.
113The content of this file is the name of the profile that should be "upgraded 113The content of this file is the name of the profile that should be "upgraded
114to"; portage uses this information to automatically warn you when you should 114to"; portage uses this information to automatically warn you when you should
115update to a new profile. 115update to a new profile.
116</p> 116</p>
117 117
118<p> 118<p>
119There are various reasons that a new profile may be created: the release of 119There are various reasons that a new profile may be created: the release of
120new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or 120new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or
121<c>glibc</c>) that are incompatible with previous versions, a change in 121<c>glibc</c>) that are incompatible with previous versions, a change in
122the default USE flags or in the virtual mappings, or maybe a change in 122the default USE flags or in the virtual mappings, or maybe a change in
123system-wide settings (such as defining udev to be the default manager 123system-wide settings.
124for <path>/dev</path> instead of devfs).
125</p> 124</p>
126 125
127</body> 126</body>
128</section> 127</section>
129</chapter> 128</chapter>
130 129
131<chapter> 130<chapter>
132<title>Keeping up with new releases</title> 131<title>Keeping up with new releases</title>
133<section> 132<section>
134<title>Releases without profile changes</title> 133<title>Releases without profile changes</title>
135<body> 134<body>
136 135
137<p> 136<p>
138If a new Gentoo release is announced that does not include a new profile 137If a new Gentoo release is announced that does not include a new profile
139then you can safely pretend that it never happened :). 138then you can safely pretend that it never happened :).
141 140
142<p> 141<p>
143If you update your installed packages 142If you update your installed packages
144<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in 143<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
145the Gentoo Handbook</uri>, then your system will be exactly the same as one 144the Gentoo Handbook</uri>, then your system will be exactly the same as one
146that has been installed using the new release. 145that has been installed using the new release.
147</p> 146</p>
148 147
149</body> 148</body>
150</section> 149</section>
151<section> 150<section>
152<title>Releases with profile changes</title> 151<title>Releases with profile changes</title>
153<body> 152<body>
154 153
155<p> 154<p>
156If a release (such as 2005.0) introduces a new profile, you have the choice 155If a release (such as 2005.1 for x86) introduces a new profile, you have the
157to migrate to the new profile. 156choice to migrate to the new profile.
158</p> 157</p>
159 158
160<p> 159<p>
161Naturally, you are not forced to do so, and you can continue to use the old 160Naturally, you are not forced to do so, and you can continue to use the old
162profile and just update your packages 161profile and just update your packages
163<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained 162<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained
164in the Gentoo Handbook</uri>. 163in the Gentoo Handbook</uri>.
165</p> 164</p>
166 165
167<p> 166<p>
168However, Gentoo strongly recommends updating your profile if it becomes 167However, Gentoo strongly recommends updating your profile if it becomes
169deprecated. When this happens, it means that Gentoo developers no longer 168deprecated. When this happens, it means that Gentoo developers no longer
170plan on supporting it. Using the table below, you can quickly check to 169plan on supporting it. Using the table below, you can quickly check to
171see what profiles are currently supported. 170see what profiles are currently supported.
172</p> 171</p>
193<body> 192<body>
194 193
195<p> 194<p>
196The following profiles are officially supported by Gentoo developers: 195The following profiles are officially supported by Gentoo developers:
197</p> 196</p>
198 197
199<table> 198<table>
200<tr> 199<tr>
201 <th>Architecture</th> 200 <th>Architecture</th>
202 <th>Most recent profiles</th> 201 <th>Most recent profiles</th>
203 <th>Other supported profiles</th> 202 <th>Other supported profiles</th>
204</tr> 203</tr>
205<tr> 204<tr>
206 <th>alpha</th> 205 <th>alpha</th>
207 <ti>2005.0, 2005.0/2.4</ti> 206 <ti>2005.0, 2005.0/2.4</ti>
207 <ti></ti>
208</tr>
209<tr>
210 <th>arm</th>
208 <ti>2004.3</ti> 211 <ti>2004.3</ti>
209</tr>
210<tr>
211 <th>arm</th>
212 <ti>2005.0</ti> 212 <ti></ti>
213 <ti>2004.3</ti>
214</tr> 213</tr>
215<tr> 214<tr>
216 <th>amd64</th> 215 <th>amd64</th>
217 <ti>2005.0, 2005.0/no-multilib</ti> 216 <ti>2005.1, 2005.1/no-multilib</ti>
218 <ti>2004.3</ti> 217 <ti>2005.0, 2005.0/no-multilib, 2004.3</ti>
219</tr> 218</tr>
220<tr> 219<tr>
221 <th>hppa</th> 220 <th>hppa</th>
222 <ti>2005.0, 2005.0/2.4</ti> 221 <ti>2005.0, 2005.0/2.4</ti>
223 <ti>2004.3, 2004.2</ti> 222 <ti>2004.3, 2004.2</ti>
224</tr> 223</tr>
225<tr> 224<tr>
226 <th>ia64</th> 225 <th>ia64</th>
227 <ti>2005.0</ti> 226 <ti>2005.0</ti>
228 <ti></ti> 227 <ti>2004.3</ti>
229</tr> 228</tr>
230<tr> 229<tr>
231 <th>ppc</th> 230 <th>ppc</th>
232 <ti>2005.0</ti> 231 <ti>2005.1</ti>
233 <ti>2004.3, 2004.0</ti> 232 <ti>2005.0, 2004.3, 2004.0</ti>
234</tr> 233</tr>
235<tr> 234<tr>
236 <th>mips</th> 235 <th>mips</th>
237 <ti>2005.0</ti> 236 <ti>2005.0</ti>
238 <ti>2004.2</ti> 237 <ti>2004.2</ti>
239</tr> 238</tr>
240<tr> 239<tr>
241 <th>s390</th> 240 <th>s390</th>
241 <ti>2004.3</ti>
242 <ti></ti>
243</tr>
244<tr>
245 <th>sparc</th>
246 <ti>2005.1</ti>
242 <ti>2005.0</ti> 247 <ti>2005.0</ti>
243 <ti>2004.3</ti>
244</tr>
245<tr>
246 <th>sparc</th>
247 <ti>2005.0</ti>
248 <ti>2004.3, 2004.0</ti>
249</tr> 248</tr>
250<tr> 249<tr>
251 <th>x86</th> 250 <th>x86</th>
251 <ti>2005.1, 2005.1/2.4</ti>
252 <ti>2005.0, 2005.0/2.4</ti> 252 <ti>2005.0, 2005.0/2.4</ti>
253 <ti>2004.3, 2004.2, 2004.0</ti>
254</tr> 253</tr>
255</table> 254</table>
256 255
257</body> 256</body>
258</section> 257</section>
259</chapter> 258</chapter>
260 259
261<chapter id="instructions"> 260<chapter id="instructions">
262<title>Profile updating instructions</title> 261<title>Profile updating instructions</title>
262<section>
263<title>Updating to 2005.1</title>
264<body>
265
266<p>
267To switch to the 2005.1 profile, point the <path>/etc/make.profile</path>
268symlink to the new location. Make sure your Portage is updated before you
269change your profile.
270</p>
271
272<pre caption="Changing to a 2005.1 profile">
273# <i>rm /etc/make.profile</i>
274# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
275</pre>
276
277<p>
278<b>All archs</b> - There are no fundamental changes in this profile. No
279specific action needs to be performed.
280</p>
281
282<p>
283<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged
284and a number of subprofiles for specific subarchitectures were created. Make
285sure you choose the correct subprofile for your system when migrating to a
2862005.1 profile.
287</p>
288
289</body>
290</section>
263<section> 291<section>
264<title>Updating to 2005.0</title> 292<title>Updating to 2005.0</title>
265<body> 293<body>
266 294
267<p> 295<p>
268With the introduction of 2005.0, several architectures have decided to define 296With the introduction of 2005.0, several architectures have decided to define
269additional profiles. Make sure you read the description of said profiles before 297additional profiles. Make sure you read the description of said profiles before
270you decide to migrate to one of them. Most architectures now also default to the 298you decide to migrate to one of them. Most architectures now also default to the
2712.6 kernel tree where 2.4 was chosen previously. 2992.6 kernel tree where 2.4 was chosen previously.
272</p> 300</p>
273 301
274<p> 302<p>
275Some architectures require a bit more actions to be completed in order to 303Some architectures require a bit more actions to be completed in order to
276convert from one profile to another. If that is the case, the step-by-step 304convert from one profile to another. If that is the case, the step-by-step
277guides are linked from the table. 305guides are linked from the table.

Legend:
Removed from v.1.23  
changed lines
  Added in v.1.24

  ViewVC Help
Powered by ViewVC 1.1.20