/[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.20
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.20 2005/03/28 11:41:41 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">
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.8</version> 20<version>2.9</version>
21<date>2005-01-22</date> 21<date>2005-03-28</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
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
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 default x86 2005.0 profile can be found
102(old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style 103at <path>/usr/portage/profiles/default-linux/x86/2005.0</path>.
103location - only for use with Portage 2.0.51 and later). With respect to new-style profile directories, note that the files in 104The files in the parent directories are part of the profile as well (and
104parent directories are part of the profile (and are therefore shared 105are therefore shared by different subprofiles). This is why we call these
105by different subprofiles). 106<e>cascaded profiles</e>.
106</p> 107</p>
107 108
108<p> 109<p>
109Profiles 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>
110along with the current ones, but they are marked as deprecated. When that happens a 111along 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 112happens 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 113The 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. 114to"; portage uses this information to automatically warn you when you should
114</p> 115update to a new profile.
115
116<p> 116</p>
117
118<p>
117There are various reasons that a new profile may be created: the release of new 119There 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>) 120new 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 121<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 122the 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). 123system-wide settings (such as defining udev to be the default manager
124for <path>/dev</path> instead of devfs).
122</p> 125</p>
123 126
124</body> 127</body>
125</section> 128</section>
126</chapter> 129</chapter>
130<section> 133<section>
131<title>Releases without profile changes</title> 134<title>Releases without profile changes</title>
132<body> 135<body>
133 136
134<p> 137<p>
135If a new Gentoo release is announced that does not include a new profile (such 138If a new Gentoo release is announced that does not include a new profile
136as the 2004.1 release for x86), then you can safely pretend that it never 139then you can safely pretend that it never happened :).
137happened :).
138</p> 140</p>
139 141
140<p> 142<p>
141If you update your installed packages 143If you update your installed packages
142<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in 144<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
149<section> 151<section>
150<title>Releases with profile changes</title> 152<title>Releases with profile changes</title>
151<body> 153<body>
152 154
153<p> 155<p>
154If a release introduces a new profile, you have the choice to migrate to the 156If a release (such as 2005.0) introduces a new profile, you have the choice
155new profile. 157to migrate to the new profile.
156</p>
157
158<p> 158</p>
159
160<p>
159Naturally, you are not forced to do so, and you can continue to use the old profile 161Naturally, you are not forced to do so, and you can continue to use the old
160and just update your packages 162profile and just update your packages
161<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in 163<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained
162the Gentoo Handbook</uri>. 164in the Gentoo Handbook</uri>.
163</p>
164
165<p> 165</p>
166
167<p>
166However, Gentoo strongly recommends updating your profile if it becomes deprecated. 168However, Gentoo strongly recommends updating your profile if it becomes
167When this happens, it means that Gentoo developers no longer plan on supporting it. 169deprecated. 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. 170plan on supporting it. Using the table below, you can quickly check to
171see what profiles are currently supported.
169</p> 172</p>
170 173
171<p> 174<p>
172If you decide to migrate to the new profile, then you will have to manually 175If 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 176perform the update. The way you update may vary significantly from release
174depends on how deep the modifications introduced in the new profile are. 177to release; it depends on how deep the modifications introduced in the new
178profile are.
175</p> 179</p>
176 180
177<p> 181<p>
178In the simplest case you only have to change the <path>/etc/make.profile</path> 182In 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 183symlink, 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 184while doing a neat voodoo dance. Migration is usually covered in the release
181notes (e.g. <uri 185notes. You can also find <uri link="#instructions">instructions</uri> at the
182link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3 186end of this guide.
183release notes</uri>). You can also find <uri
184link="#instructions">instructions</uri> at the end of this guide.
185</p> 187</p>
186 188
187</body> 189</body>
188</section> 190</section>
189<section> 191<section>
195</p> 197</p>
196 198
197<table> 199<table>
198<tr> 200<tr>
199 <th>Architecture</th> 201 <th>Architecture</th>
200 <th>Most recent profile</th> 202 <th>Most recent profiles</th>
201 <th>Other supported profiles</th> 203 <th>Other supported profiles</th>
202</tr> 204</tr>
203<tr> 205<tr>
204 <th>alpha</th> 206 <th>alpha</th>
207 <ti>2005.0, 2005.0/2.4</ti>
205 <ti>2004.3</ti> 208 <ti>2004.3</ti>
206 <ti></ti>
207</tr> 209</tr>
208<tr> 210<tr>
209 <th>arm</th> 211 <th>arm</th>
212 <ti>2005.0</ti>
210 <ti>2004.3</ti> 213 <ti>2004.3</ti>
211 <ti></ti>
212</tr> 214</tr>
213<tr> 215<tr>
214 <th>amd64</th> 216 <th>amd64</th>
217 <ti>2005.0, 2005.0/no-multilib</ti>
215 <ti>2004.3</ti> 218 <ti>2004.3</ti>
216 <ti>2004.2, 2004.0</ti>
217</tr> 219</tr>
218<tr> 220<tr>
219 <th>hppa</th> 221 <th>hppa</th>
222 <ti>2005.0, 2005.0/2.4</ti>
223 <ti>2004.3, 2004.2</ti>
224</tr>
225<tr>
226 <th>ia64</th>
227 <ti>2005.0</ti>
228 <ti></ti>
229</tr>
230<tr>
231 <th>ppc</th>
232 <ti>2005.0</ti>
233 <ti>2004.3, 2004.0</ti>
234</tr>
235<tr>
236 <th>mips</th>
237 <ti>2005.0</ti>
238 <ti>2004.2</ti>
239</tr>
240<tr>
241 <th>s390</th>
242 <ti>2005.0</ti>
220 <ti>2004.3</ti> 243 <ti>2004.3</ti>
221 <ti>2004.2</ti>
222</tr>
223<tr>
224 <th>ia64</th>
225 <ti>2004.3</ti>
226 <ti></ti>
227</tr>
228<tr>
229 <th>ppc</th>
230 <ti>2004.3</ti>
231 <ti>2004.0</ti>
232</tr>
233<tr>
234 <th>mips</th>
235 <ti>2004.2</ti>
236 <ti></ti>
237</tr>
238<tr>
239 <th>s390</th>
240 <ti>2004.3</ti>
241 <ti></ti>
242</tr> 244</tr>
243<tr> 245<tr>
244 <th>sparc</th> 246 <th>sparc</th>
245 <ti>2004.3</ti>
246 <ti>2004.0</ti> 247 <ti>2005.0</ti>
248 <ti>2004.3, 2004.0</ti>
247</tr> 249</tr>
248<tr> 250<tr>
249 <th>x86</th> 251 <th>x86</th>
250 <ti>2004.3</ti> 252 <ti>2005.0, 2005.0/2.4</ti>
251 <ti>2004.2, 2004.0</ti> 253 <ti>2004.3, 2004.2, 2004.0</ti>
252</tr> 254</tr>
253</table> 255</table>
254 256
255</body> 257</body>
256</section> 258</section>
257</chapter> 259</chapter>
258 260
259<chapter id="instructions"> 261<chapter id="instructions">
260<title>Profile updating instructions</title> 262<title>Profile updating instructions</title>
263<section>
264<title>Updating to 2005.0</title>
265<body>
266
267<p>
268With the introduction of 2005.0, several architectures have decided to define
269additional 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
2712.6 kernel tree where 2.4 was chosen previously.
272</p>
273
274<p>
275Some 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
277guides are linked from the table.
278</p>
279
280<table>
281<tr>
282 <th>Profile</th>
283 <th>Description</th>
284 <th>Specific Upgrade Guide</th>
285</tr>
286<tr>
287 <ti>default-linux/alpha/2005.0</ti>
288 <ti>Default Alpha 2005.0 profile for 2.6 kernels</ti>
289 <ti></ti>
290</tr>
291<tr>
292 <ti>default-linux/alpha/2005.0/2.4</ti>
293 <ti>Alpha 2005.0 profile for 2.4 kernels</ti>
294 <ti></ti>
295</tr>
296<tr>
297 <ti>default-linux/amd64/2005.0</ti>
298 <ti>Default AMD64 2005.0 profile for 2.6 kernels</ti>
299 <ti>
300 <uri link="/proj/en/base/amd64/2005.0-upgrade-amd64.xml">Upgrading to
301 2005.0</uri>
302 </ti>
303</tr>
304<tr>
305 <ti>default-linux/amd64/2005.0/no-multilib</ti>
306 <ti>AMD64 2005.0 profile for multilib-disabled system installations</ti>
307 <ti>
308 <uri link="/proj/en/base/amd64/2005.0-upgrade-amd64.xml">Upgrading to
309 2005.0</uri>
310 </ti>
311</tr>
312<tr>
313 <ti>default-linux/arm/2005.0</ti>
314 <ti>Default ARM 2005.0 profile for 2.6 kernels</ti>
315 <ti></ti>
316</tr>
317<tr>
318 <ti>default-linux/hppa/2005.0</ti>
319 <ti>Default HPPA 2005.0 profile for 2.6 kernels</ti>
320 <ti></ti>
321</tr>
322<tr>
323 <ti>default-linux/hppa/2005.0/2.4</ti>
324 <ti>HPPA 2005.0 profile for 2.4 kernels</ti>
325 <ti></ti>
326</tr>
327<tr>
328 <ti>default-linux/mips/2005.0</ti>
329 <ti>Default MIPS 2005.0 profile</ti>
330 <ti></ti>
331</tr>
332<tr>
333 <ti>default-linux/mips/cobalt/2005.0</ti>
334 <ti>Cobalt specific MIPS 2005.0 profile</ti>
335 <ti></ti>
336</tr>
337<tr>
338 <ti>default-linux/mips/mips64/n32/2005.0</ti>
339 <ti>2005.0 profile for n32-supporting MIPS platforms</ti>
340 <ti></ti>
341</tr>
342<tr>
343 <ti>default-linux/mips/mips64/ip28/2005.0</ti>
344 <ti>Indigo2 Impact specific 64-bit 2005.0 profile</ti>
345 <ti></ti>
346</tr>
347<tr>
348 <ti>default-linux/mips/mips64/2005.0</ti>
349 <ti>64-bit MIPS 2005.0 profile</ti>
350 <ti></ti>
351</tr>
352<tr>
353 <ti>default-linux/ppc/2005.0</ti>
354 <ti>Default PPC 2005.0 profile for 2.6 kernels</ti>
355 <ti></ti>
356</tr>
357<tr>
358 <ti>default-linux/ppc64/2005.0</ti>
359 <ti>Default PPC64 2005.0 profile for 2.6 kernels</ti>
360 <ti></ti>
361</tr>
362<tr>
363 <ti>default-linux/s390/2005.0</ti>
364 <ti>Default S390 2005.0 profile</ti>
365 <ti></ti>
366</tr>
367<tr>
368 <ti>default-linux/sparc/sparc32/2005.0</ti>
369 <ti>Default Sparc 32-bit 2005.0 profile</ti>
370 <ti></ti>
371</tr>
372<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
373 No subprofiles for sparc
374<tr>
375 <ti>default-linux/sparc/sparc32/2005.0/2.6</ti>
376 <ti>Sparc 32-bit 2005.0 profile for 2.6 kernels</ti>
377 <ti></ti>
378</tr>
379-->
380<tr>
381 <ti>default-linux/sparc/sparc64/2005.0</ti>
382 <ti>Default Sparc 64-bit 2005.0 profile</ti>
383 <ti></ti>
384</tr>
385<!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm
386 No subprofiles for sparc
387<tr>
388 <ti>default-linux/sparc/sparc64/2005.0/2.6</ti>
389 <ti>Sparc 64-bit 2005.0 profile for 2.6 kernels</ti>
390 <ti></ti>
391</tr>
392-->
393<tr>
394 <ti>default-linux/x86/2005.0</ti>
395 <ti>Default x86 2005.0 profile for 2.6 kernels</ti>
396 <ti></ti>
397</tr>
398<tr>
399 <ti>default-linux/x86/2005.0/2.4</ti>
400 <ti>x86 2005.0 profile for 2.4 kernels</ti>
401 <ti></ti>
402</tr>
403</table>
404
405<p>
406To switch to the selected profile, point the <path>/etc/make.profile</path>
407symlink to the new location. Make sure your Portage is updated before you change
408your profile!
409</p>
410
411<pre caption="Changing to a 2005.0 profile">
412# <i>rm /etc/make.profile</i>
413# <i>ln -s ../usr/portage/profiles/</i>&lt;selected profile&gt;<i> /etc/make.profile</i>
414</pre>
415
416<p>
417If you are running a Linux 2.4-based system but want to migrate to a 2.6-based
418kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo
419Linux 2.6 Migration Guide</uri>.
420</p>
421
422</body>
423</section>
261<section> 424<section>
262<title>Updating to 2004.3</title> 425<title>Updating to 2004.3</title>
263<body> 426<body>
264 427
265<p> 428<p>
297<path>/var/lib/portage/world</path> after the profile switch, or manually 460<path>/var/lib/portage/world</path> after the profile switch, or manually
298emerge them. 461emerge them.
299</p> 462</p>
300 463
301<p> 464<p>
302<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/devfs</c> 465<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, 466<c>sys-fs/devfs</c> for newly installed machines. This has no
304though. 467effect on already installed machines, though.
305</p> 468</p>
306 469
307</body> 470</body>
308</section> 471</section>
309<section> 472<section>
310<title>Updating to 2004.2</title> 473<title>Updating to 2004.2</title>
311<body> 474<body>
312 475
313<p> 476<p>
314To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink 477To switch to the 2004.2 profile, point the <path>/etc/make.profile</path>
315to the new location: 478symlink to the new location:
316</p> 479</p>
317 480
318<warn> 481<warn>
319Don't forget to upgrade Portage <e>before</e> you change your profile!!! 482Don't forget to upgrade Portage <e>before</e> you change your profile!!!
320</warn> 483</warn>
344<section> 507<section>
345<title>Updating to 2004.0</title> 508<title>Updating to 2004.0</title>
346<body> 509<body>
347 510
348<p> 511<p>
349To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> symlink 512To switch to the 2004.0 profile, point the <path>/etc/make.profile</path>
350to the new location: 513symlink to the new location:
351</p> 514</p>
352 515
353<pre caption="Updating the /etc/make.profile symlink"> 516<pre caption="Updating the /etc/make.profile symlink">
354<comment>substitute &lt;arch&gt; with your arch</comment> 517<comment>substitute &lt;arch&gt; with your arch</comment>
355# <i>rm /etc/make.profile</i> 518# <i>rm /etc/make.profile</i>

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

  ViewVC Help
Powered by ViewVC 1.1.20