/[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.13
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.13 2004/11/08 10:00:49 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">
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.5</version>
21<date>September 25, 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>
70 <li> 70 <li>
71 A new release means new LiveCDs with bugfixes and more features. 71 A new release means new LiveCDs with bugfixes and more features.
72 </li> 72 </li>
73 <li> 73 <li>
74 A new release provides an updated set of GRP packages, so that users that 74 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 75 choose "the fast way" to install (stage3 + precompiled packages) end up
76 with a system that is not outdated. 76 with a system that is not outdated.
77 </li> 77 </li>
78 <li> 78 <li>
79 Finally, a new release may, from time to time, implement some features that 79 Finally, a new release may, from time to time, implement some features that
80 are incompatible with previous releases. 80 are incompatible with previous releases.
87that it provides a new <e>profile</e>. 87that it provides a new <e>profile</e>.
88</p> 88</p>
89 89
90<p> 90<p>
91A <e>profile</e> is a set of configuration files, stored in a subdirectory of 91A <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 92<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 93that are considered <e>system</e> packages, the default USE flags, the default
94mapping for virtual packages, and architecture that 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
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
108<p> 113<p>
109Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> 114Profiles 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 115along with the current ones, but they are marked as deprecated. When that happens a
111file named <path>deprecated</path> is put in the profile directory. The content 116file named <path>deprecated</path> is put in the profile directory. The content
112of this file is the name of the profile that should be "upgraded to"; portage uses 117of this file is the name of the profile that should be "upgraded to"; portage uses
114</p> 119</p>
115 120
116<p> 121<p>
117There are various reasons that a new profile may be created: the release of new 122There are various reasons that a new profile may be created: the release of new
118versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or <c>glibc</c>) 123versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or <c>glibc</c>)
119that are incompatible with previous versions, a change in the default USE flags, or 124that are incompatible with previous versions, a change in the default USE flags or
120in the virtual mappings, or maybe a change in system-wide settings (such as defining 125in the virtual mappings, or maybe a change in system-wide settings (such as defining
121udev to be the default manager for <path>/dev</path> instead of devfs). 126udev to be the default manager for <path>/dev</path> instead of devfs).
122</p> 127</p>
123 128
124</body> 129</body>
169</p> 174</p>
170 175
171<p> 176<p>
172If you decide to migrate to the new profile, then you will have to manually 177If 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 178perform the update. The way you update may vary significantly from release to release; it
174depends on how deep the modifications introduced in the new profile. 179depends on how deep the modifications introduced in the new profile are.
175</p> 180</p>
176 181
177<p> 182<p>
178In the simplest case you only have to change the <path>/etc/make.profile</path> 183In 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 184symlink, 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 185while 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. 186notes (e.g. <uri
187link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3
188release notes</uri>). You can also find <uri
189link="#instructions">instructions</uri> at the end of this guide.
182</p> 190</p>
183 191
184</body> 192</body>
185</section> 193</section>
186<section> 194<section>
196 <th>Architecture</th> 204 <th>Architecture</th>
197 <th>Most recent profile</th> 205 <th>Most recent profile</th>
198 <th>Other supported profiles</th> 206 <th>Other supported profiles</th>
199</tr> 207</tr>
200<tr> 208<tr>
209 <th>alpha</th>
210 <ti>2004.3</ti>
211 <ti></ti>
212</tr>
213<tr>
201 <th>arm</th> 214 <th>arm</th>
215 <ti>2004.3</ti>
216 <ti></ti>
217</tr>
218<tr>
219 <th>amd64</th>
220 <ti>2004.3</ti>
221 <ti>2004.2, 2004.0</ti>
222</tr>
223<tr>
224 <th>hppa</th>
225 <ti>2004.3</ti>
226 <ti>2004.2</ti>
227</tr>
228<tr>
229 <th>ia64</th>
230 <ti>2004.3</ti>
231 <ti></ti>
232</tr>
233<tr>
234 <th>ppc</th>
235 <ti>2004.3</ti>
202 <ti>2004.0</ti> 236 <ti>2004.0</ti>
203 <ti></ti>
204</tr>
205<tr> 237</tr>
238<tr>
206 <th>amd64</th> 239 <th>mips</th>
207 <ti>2004.2</ti> 240 <ti>2004.2</ti>
241 <ti></ti>
242</tr>
243<tr>
244 <th>s390</th>
245 <ti>2004.3</ti>
246 <ti></ti>
247</tr>
248<tr>
249 <th>sparc</th>
250 <ti>2004.3</ti>
208 <ti>2004.0</ti> 251 <ti>2004.0</ti>
209</tr> 252</tr>
210<tr> 253<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> 254 <th>x86</th>
242 <ti>2004.2</ti> 255 <ti>2004.3</ti>
243 <ti>2004.0, 1.4</ti> 256 <ti>2004.2, 2004.0</ti>
244</tr> 257</tr>
245</table> 258</table>
246 259
247</body> 260</body>
248</section> 261</section>
249</chapter> 262</chapter>
250 263
251<chapter> 264<chapter id="instructions">
252<title>Profile updating instructions</title> 265<title>Profile updating instructions</title>
266<section>
267<title>Updating to 2004.3</title>
268<body>
269
270<p>
271With the introduction of the 2004.3 profiles, users are not going to see huge
272modifications of their systems (see below for details). However, Gentoo
273developers 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
275profiles that follow the new layout of the <path>/usr/portage/profiles</path>
276directory, for instance
277<path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
278Portage 2.0.51 or later).
279</p>
280
281<p>
282To switch to the 2004.3 profile, point the <path>/etc/make.profile</path>
283symlink to the new location:
284</p>
285
286<pre caption="Updating the /etc/make.profile symlink">
287<comment>substitute &lt;arch&gt; with your arch</comment>
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>
290</pre>
291
292<p>
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
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
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
299emerge them.
300</p>
301
302<p>
303<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/devfs</c>
304for newly installed machines. This has no effect on already installed machines,
305though.
306</p>
307
308</body>
309</section>
253<section> 310<section>
254<title>Updating to 2004.2</title> 311<title>Updating to 2004.2</title>
255<body> 312<body>
256 313
257<p> 314<p>

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

  ViewVC Help
Powered by ViewVC 1.1.20