/[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.9 Revision 1.10
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.9 2004/08/13 13:42:30 swift Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.10 2004/09/25 12:49:11 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">
9 <mail link="g.guidi@sns.it">Gregorio Guidi</mail> 9 <mail link="g.guidi@sns.it">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/1.0 -->
18<license/> 18<license/>
19 19
20<version>2.2</version> 20<version>2.3</version>
21<date>August 13, 2004</date> 21<date>September 25, 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>
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
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 architecture that 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
100<path>/usr/portage/profiles</path> which holds the profile files. For instance, 100<path>/usr/portage/profiles</path> which holds the profile files. For instance,
101the x86 2004.2 profile can be found at <path>/usr/portage/profiles/default-x86-2004.2</path> 101the x86 2004.2 profile can be found at <path>/usr/portage/profiles/default-x86-2004.2</path>
102(old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style 102(old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style
103location). 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<p> 108<p>
109Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> 109Profiles 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 110along 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 111file 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 112of this file is the name of the profile that should be "upgraded to"; portage uses
113this information to automatically warn you when you should update to a new profile. 113this information to automatically warn you when you should update to a new profile.
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>)

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

  ViewVC Help
Powered by ViewVC 1.1.20