/[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.12 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.12 2004/11/06 17:37:50 neysx 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/2.0 --> 17<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
18<license/> 18<license/>
19 19
20<version>2.4</version> 20<version>2.8</version>
21<date>November 5, 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=1">A Portage 50link="/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=1">A Portage
51Introduction</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>
276<p> 276<p>
277To switch to the 2004.3 profile, point the <path>/etc/make.profile</path> 277To switch to the 2004.3 profile, point the <path>/etc/make.profile</path>
278symlink to the new location: 278symlink to the new location:
279</p> 279</p>
280 280
281<warn>
282Don't forget to upgrade Portage <e>before</e> you change your profile!!!
283</warn>
284
281<pre caption="Updating the /etc/make.profile symlink"> 285<pre caption="Updating the /etc/make.profile symlink">
282<comment>substitute &lt;arch&gt; with your arch</comment> 286<comment>substitute &lt;arch&gt; with your arch</comment>
283# <i>rm /etc/make.profile</i> 287# <i>rm /etc/make.profile</i>
284# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i> 288# <i>ln -s ../usr/portage/profiles/default-linux/&lt;arch&gt;/2004.3 /etc/make.profile</i>
285</pre> 289</pre>
286 290
287<p> 291<p>
288<b>All archs</b> - As said above, there are no big changes introduced in this 292<b>All archs</b> - As said above, there are no big changes introduced in this
289profile. However, it should be noted that <c>sys-apps/slocate</c> and 293profile. However, it should be noted that <c>sys-apps/slocate</c> and
290<c>net-misc/dhcpcd</c> are no longer considered system packages. This means 294<c>net-misc/dhcpcd</c> are no longer considered system packages. This means
291that if you run <c>emerge depclean</c>, Portage will try to remove them from 295that if you run <c>emerge --depclean</c>, Portage will try to remove them from
292your system. If you need any of those packages, add them to 296your system. If you need any of those packages, add them to
293<path>/var/lib/portage/world</path> after the profile switch, or manually 297<path>/var/lib/portage/world</path> after the profile switch, or manually
294emerge them. 298emerge them.
295</p> 299</p>
296 300
308 312
309<p> 313<p>
310To 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
311to the new location: 315to the new location:
312</p> 316</p>
317
318<warn>
319Don't forget to upgrade Portage <e>before</e> you change your profile!!!
320</warn>
313 321
314<pre caption="Updating the /etc/make.profile symlink"> 322<pre caption="Updating the /etc/make.profile symlink">
315<comment>substitute &lt;arch&gt; with your arch</comment> 323<comment>substitute &lt;arch&gt; with your arch</comment>
316# <i>rm /etc/make.profile</i> 324# <i>rm /etc/make.profile</i>
317# <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.12  
changed lines
  Added in v.1.18

  ViewVC Help
Powered by ViewVC 1.1.20