/[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.10 Revision 1.18
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.10 2004/09/25 12:49:11 swift Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.18 2005/01/25 11:48:14 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="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>
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 beginning,
44Gentoo was designed around the concept of fast, incremental updates. 44Gentoo was designed around the concept of fast, incremental updates.
45</p> 45</p>
46 46
47<p> 47<p>
48Ideally, you install once and then do not to bother with releases: 48Ideally, you install once and never bother with releases: just follow the
49just follow the instructions in 49instructions in <uri
50<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">Portage and 50link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage
51Software</uri> in the 51Introduction</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 52that 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 53usually 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. 54to be done manually.
55</p> 55</p>
56 56
57</body> 57</body>
58</section> 58</section>
59<section> 59<section>
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
114</p> 114</p>
115 115
116<p> 116<p>
117There are various reasons that a new profile may be created: the release of new 117There 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>) 118versions 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 119that 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 120in 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). 121udev to be the default manager for <path>/dev</path> instead of devfs).
122</p> 122</p>
123 123
124</body> 124</body>
137happened :). 137happened :).
138</p> 138</p>
139 139
140<p> 140<p>
141If you update your installed packages 141If you update your installed packages
142<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">as explained in 142<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
143the Gentoo Handbook</uri>, then your system will be exactly the same as one 143the Gentoo Handbook</uri>, then your system will be exactly the same as one
144that has been installed using the new release. 144that has been installed using the new release.
145</p> 145</p>
146 146
147</body> 147</body>
156</p> 156</p>
157 157
158<p> 158<p>
159Naturally, you are not forced to do so, and you can continue to use the old profile 159Naturally, you are not forced to do so, and you can continue to use the old profile
160and just update your packages 160and just update your packages
161<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2">as explained in 161<uri link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">as explained in
162the Gentoo Handbook</uri>. 162the Gentoo Handbook</uri>.
163</p> 163</p>
164 164
165<p> 165<p>
166However, Gentoo strongly recommends updating your profile if it becomes deprecated. 166However, Gentoo strongly recommends updating your profile if it becomes deprecated.
169</p> 169</p>
170 170
171<p> 171<p>
172If you decide to migrate to the new profile, then you will have to manually 172If 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 173perform 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. 174depends on how deep the modifications introduced in the new profile are.
175</p> 175</p>
176 176
177<p> 177<p>
178In the simplest case you only have to change the <path>/etc/make.profile</path> 178In 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 179symlink, 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 180while 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. 181notes (e.g. <uri
182link="/proj/en/releng/release/2004.3/x86-release-notes.xml">the x86 2004.3
183release notes</uri>). You can also find <uri
184link="#instructions">instructions</uri> at the end of this guide.
182</p> 185</p>
183 186
184</body> 187</body>
185</section> 188</section>
186<section> 189<section>
196 <th>Architecture</th> 199 <th>Architecture</th>
197 <th>Most recent profile</th> 200 <th>Most recent profile</th>
198 <th>Other supported profiles</th> 201 <th>Other supported profiles</th>
199</tr> 202</tr>
200<tr> 203<tr>
204 <th>alpha</th>
205 <ti>2004.3</ti>
206 <ti></ti>
207</tr>
208<tr>
201 <th>arm</th> 209 <th>arm</th>
210 <ti>2004.3</ti>
211 <ti></ti>
212</tr>
213<tr>
214 <th>amd64</th>
215 <ti>2004.3</ti>
216 <ti>2004.2, 2004.0</ti>
217</tr>
218<tr>
219 <th>hppa</th>
220 <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>
202 <ti>2004.0</ti> 231 <ti>2004.0</ti>
203 <ti></ti>
204</tr>
205<tr> 232</tr>
233<tr>
206 <th>amd64</th> 234 <th>mips</th>
207 <ti>2004.2</ti> 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>
243<tr>
244 <th>sparc</th>
245 <ti>2004.3</ti>
208 <ti>2004.0</ti> 246 <ti>2004.0</ti>
209</tr> 247</tr>
210<tr> 248<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> 249 <th>x86</th>
242 <ti>2004.2</ti> 250 <ti>2004.3</ti>
243 <ti>2004.0, 1.4</ti> 251 <ti>2004.2, 2004.0</ti>
244</tr> 252</tr>
245</table> 253</table>
246 254
247</body> 255</body>
248</section> 256</section>
249</chapter> 257</chapter>
250 258
251<chapter> 259<chapter id="instructions">
252<title>Profile updating instructions</title> 260<title>Profile updating instructions</title>
261<section>
262<title>Updating to 2004.3</title>
263<body>
264
265<p>
266With the introduction of the 2004.3 profiles, users are not going to see huge
267modifications of their systems (see below for details). However, Gentoo
268developers decided to push out this new profile and to deprecate quite a few of
269the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the
270profiles that follow the new layout of the <path>/usr/portage/profiles</path>
271directory, for instance
272<path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by
273Portage 2.0.51 or later).
274</p>
275
276<p>
277To switch to the 2004.3 profile, point the <path>/etc/make.profile</path>
278symlink to the new location:
279</p>
280
281<warn>
282Don't forget to upgrade Portage <e>before</e> you change your profile!!!
283</warn>
284
285<pre caption="Updating the /etc/make.profile symlink">
286<comment>substitute &lt;arch&gt; with your arch</comment>
287# <i>rm /etc/make.profile</i>
288# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i>
289</pre>
290
291<p>
292<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
294<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
296your system. If you need any of those packages, add them to
297<path>/var/lib/portage/world</path> after the profile switch, or manually
298emerge them.
299</p>
300
301<p>
302<b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of <c>sys-fs/devfs</c>
303for newly installed machines. This has no effect on already installed machines,
304though.
305</p>
306
307</body>
308</section>
253<section> 309<section>
254<title>Updating to 2004.2</title> 310<title>Updating to 2004.2</title>
255<body> 311<body>
256 312
257<p> 313<p>
258To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink 314To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink
259to the new location: 315to the new location:
260</p> 316</p>
317
318<warn>
319Don't forget to upgrade Portage <e>before</e> you change your profile!!!
320</warn>
261 321
262<pre caption="Updating the /etc/make.profile symlink"> 322<pre caption="Updating the /etc/make.profile symlink">
263<comment>substitute &lt;arch&gt; with your arch</comment> 323<comment>substitute &lt;arch&gt; with your arch</comment>
264# <i>rm /etc/make.profile</i> 324# <i>rm /etc/make.profile</i>
265# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i> 325# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.2 /etc/make.profile</i>

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

  ViewVC Help
Powered by ViewVC 1.1.20