| 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.2 2004/05/15 01:02:37 neysx Exp $ --> |
3 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 1.39 2008/03/05 08:26:01 nightmorph 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 | <author title="Editor"> |
|
|
12 | <mail link="wolf31o2@gentoo.org">Chris Gianelloni</mail> |
|
|
13 | </author> |
|
|
14 | <author title="Editor"> |
|
|
15 | <mail link="nightmorph@gentoo.org">Joshua Saddler</mail> |
|
|
16 | </author> |
| 11 | |
17 | |
| 12 | <abstract> |
18 | <abstract> |
| 13 | This document explains how to react when a new Gentoo release is announced. |
19 | This document explains how new Gentoo releases affect existing installs. |
| 14 | </abstract> |
20 | </abstract> |
| 15 | |
21 | |
| 16 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
22 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 17 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
23 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 18 | <license/> |
24 | <license/> |
| 19 | |
25 | |
| 20 | <version>1.1</version> |
26 | <version>2.9</version> |
| 21 | <date>May 12, 2004</date> |
27 | <date>2008-03-05</date> |
| 22 | |
28 | |
| 23 | <chapter> |
29 | <chapter> |
| 24 | <title>Gentoo and Upgrades</title> |
30 | <title>Gentoo and Upgrades</title> |
| 25 | <section> |
31 | <section> |
| 26 | <title>Philosophy</title> |
32 | <title>Philosophy</title> |
| 27 | <body> |
33 | <body> |
| 28 | |
34 | |
| 29 | <p> |
35 | <p> |
| 30 | Here in Gentoo land, the concept of upgrade is quite different with respect to |
36 | Here in Gentoo land, the concept of upgrading is quite different compared to |
| 31 | the rest of the linux world. Probably you already know that we never got in |
37 | the rest of the Linux world. You probably already know that we never got in |
| 32 | touch with the "classic" way to upgrade software in our distribution to the |
38 | touch with the "classic" way of upgrading software: waiting for a new release, |
| 33 | latest version: waiting for a new release, downloading it, burning, putting it |
39 | downloading it, burning, putting it in the cdrom drive and then following the |
| 34 | in the cdrom drive and then following the upgrade instructions. |
40 | upgrade instructions. |
| 35 | </p> |
|
|
| 36 | |
|
|
| 37 | <p> |
41 | </p> |
|
|
42 | |
|
|
43 | <p> |
| 38 | You know (you chose Gentoo, after all) that this process is extremely |
44 | You know (being a Gentoo user after all) that this process is extremely |
| 39 | frustrating for power users that want to live on the bleeding edge. Even power |
45 | frustrating for power users that want to live on the bleeding edge. Even power |
| 40 | users from other distributions must share the same feelings, given the |
46 | users from other distributions probably share the same feelings, given the |
| 41 | popularity and spread among them of tools like apt or apt-rpm, which make it |
47 | popularity and spread of tools like apt or apt-rpm which make it |
| 42 | possible to have quick and frequent updates. However, no distibution is more |
48 | possible to have quick and frequent updates. However, no distribution is more |
| 43 | suited than Gentoo to satisfy these kind of demanding users, because Gentoo was |
49 | suited than Gentoo to satisfy these kind of demanding users. From the |
| 44 | shaped from the beginning around the concept of fast, incremental updates. |
50 | beginning, Gentoo was designed around the concept of fast, incremental |
| 45 | </p> |
51 | updates. |
| 46 | |
|
|
| 47 | <p> |
52 | </p> |
| 48 | Ideally, you install once and then do not bother anymore about releases: |
53 | |
| 49 | just follow the instructions in |
54 | <p> |
|
|
55 | Ideally, you install once and never bother with releases: just follow the |
|
|
56 | instructions in <uri |
| 50 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=2">Portage and |
57 | link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">A Portage |
| 51 | Software</uri> in the |
58 | Introduction</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 |
59 | that explain how to keep your system up to date. While that's the way things |
| 53 | your system up to date. While that's the way things go usually, it can |
60 | usually go, sometimes changes are made to the core system which require updates |
| 54 | happen sometimes that developers push out, together with a new release, an |
61 | to be done manually. |
| 55 | update that touches the basics of the systems. We will consider these cases |
|
|
| 56 | below, when talking about profiles. |
|
|
| 57 | </p> |
62 | </p> |
| 58 | |
63 | |
| 59 | </body> |
64 | </body> |
| 60 | </section> |
65 | </section> |
| 61 | <section> |
66 | <section> |
| 62 | <title>Releases and Profiles</title> |
67 | <title>Releases and Profiles</title> |
| 63 | <body> |
68 | <body> |
| 64 | |
69 | |
| 65 | <p> |
70 | <p> |
| 66 | A recurring question about the Gentoo release process is: "Why roll out new |
71 | A recurring question about the Gentoo release process is: "Why roll out new |
| 67 | releases frequently, if they are not intended to let users update software?". |
72 | releases frequently, if they are not intended to let users update software?" |
| 68 | There are various reasons: |
73 | There are various reasons: |
| 69 | </p> |
74 | </p> |
| 70 | |
75 | |
| 71 | <ul> |
76 | <ul> |
| 72 | <li> |
77 | <li> |
| 73 | A new release means enhanced and more feature-rich LiveCDs. |
78 | A new release means new Installation CDs with bugfixes and more features |
| 74 | </li> |
79 | </li> |
| 75 | <li> |
80 | <li> |
| 76 | A new release provides an updated set of GRP packages, so that users that |
81 | A new release provides an updated set of GRP packages, so that users that |
| 77 | choose "the fast way" to install, stage3 + precompiled packages, end up |
82 | choose "the fast way" to install (stage3 + precompiled packages) end up |
| 78 | with a system that is not outdated. |
83 | with a system that is not outdated |
| 79 | </li> |
84 | </li> |
| 80 | <li> |
85 | <li> |
| 81 | Finally, a new release may (not frequently) implement some features that |
86 | Finally, a new release may, from time to time, implement some features that |
| 82 | are incompatible with previous releases. |
87 | are incompatible with previous releases |
| 83 | </li> |
88 | </li> |
| 84 | </ul> |
89 | </ul> |
| 85 | |
90 | |
| 86 | <p> |
91 | <p> |
| 87 | When a release provides new incompatible features, or provides a set of core |
92 | When a release includes new incompatible features, or provides a set of core |
| 88 | packages and settings that deeply modify the behavior of the system, or simply |
93 | packages and settings that deeply modify the behavior of the system, we say |
| 89 | when it makes tricky changes to some default parameters, we say that it |
|
|
| 90 | provides a new <e>profile</e>. |
94 | that it provides a new <e>profile</e>. |
| 91 | </p> |
95 | </p> |
| 92 | |
96 | |
| 93 | <p> |
97 | <p> |
| 94 | A <e>profile</e> is a set of configuration files, stored in a subdirectory of |
98 | A <e>profile</e> is a set of configuration files, stored in a subdirectory of |
| 95 | <path>/usr/portage/profiles/</path>, that describe things such as the ebuilds |
99 | <path>/usr/portage/profiles</path>, that describe things such as the ebuilds |
| 96 | that are considered <e>system</e> packages, the default USE flags, the default |
100 | that are considered <e>system</e> packages, the default USE flags, the default |
| 97 | mapping for virtual packages. |
101 | mapping for virtual packages, and the architecture on which the system is running. |
| 98 | </p> |
102 | </p> |
| 99 | |
103 | |
| 100 | <p> |
104 | <p> |
| 101 | The profile in use is determined by the symbolic link |
105 | The profile in use is determined by the symbolic link |
| 102 | <path>/etc/make.profile</path>, which points to the subdirectory of |
106 | <path>/etc/make.profile</path>, which points to a subdirectory of |
| 103 | <path>/usr/portage/profiles</path> which holds the profile files, for instance <path>/usr/portage/profiles/default-x86-2004.0</path>. |
107 | <path>/usr/portage/profiles</path> which holds the profile files. For |
|
|
108 | instance, the default x86 2007.0 profile can be found |
|
|
109 | at <path>/usr/portage/profiles/default-linux/x86/2007.0</path>. |
|
|
110 | The files in the parent directories are part of the profile as well (and |
|
|
111 | are therefore shared by different subprofiles). This is why we call these |
|
|
112 | <e>cascaded profiles</e>. |
| 104 | </p> |
113 | </p> |
| 105 | |
114 | |
| 106 | <p> |
115 | <p> |
| 107 | Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> |
116 | Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> |
| 108 | as the current ones, but they are marked as deprecated. When that happens a |
117 | along with the current ones, but they are marked as deprecated. When that |
| 109 | file named <path>deprecated</path> is put in the profile directory. The content |
118 | happens a file named <path>deprecated</path> is put in the profile directory. |
| 110 | of this file is the name of the profile that should substitute it; portage uses |
119 | The content of this file is the name of the profile that should be "upgraded |
| 111 | this information to automatically warn you about the new profile. |
120 | to"; Portage uses this information to automatically warn you when you should |
| 112 | </p> |
121 | update to a new profile. |
| 113 | |
|
|
| 114 | <p> |
122 | </p> |
| 115 | There are various reasons that justify the creation of a new profile: the |
123 | |
|
|
124 | <p> |
|
|
125 | There are various reasons that a new profile may be created: the release of |
| 116 | release of new versions of core packages (such as <c>baselayout</c>, <c>gcc</c> |
126 | new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or |
| 117 | or <c>glibc</c>) that are incompatible with previous versions, a change in the |
127 | <c>glibc</c>) that are incompatible with previous versions, a change in |
| 118 | default USE flags, or in the virtual mappings, or maybe a change in system-wide |
128 | the default USE flags or in the virtual mappings, or maybe a change in |
| 119 | settings (such as defining udev to be the default manager for <path>/dev</path> |
129 | system-wide settings. |
| 120 | instead of devfs). |
|
|
| 121 | </p> |
130 | </p> |
| 122 | |
131 | |
| 123 | </body> |
132 | </body> |
| 124 | </section> |
133 | </section> |
| 125 | </chapter> |
134 | </chapter> |
| … | |
… | |
| 129 | <section> |
138 | <section> |
| 130 | <title>Releases without profile changes</title> |
139 | <title>Releases without profile changes</title> |
| 131 | <body> |
140 | <body> |
| 132 | |
141 | |
| 133 | <p> |
142 | <p> |
| 134 | If a new Gentoo release is announced that does not include a new profile (such |
143 | If a new Gentoo release does not include a new profile then you can safely |
| 135 | as the 2004.1 release for x86), then you can safely pretend that it never |
144 | pretend that it never happened. :) |
| 136 | happened. |
|
|
| 137 | </p> |
|
|
| 138 | |
|
|
| 139 | <p> |
145 | </p> |
|
|
146 | |
|
|
147 | <p> |
| 140 | If you update your installed packages |
148 | If you update your installed packages |
| 141 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=2">as explained in |
149 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">as explained in |
| 142 | the Gentoo Handbook</uri>, then your system will be exactly the same as one |
150 | the Gentoo Handbook</uri>, then your system will be exactly the same as one |
| 143 | that has been installed using the new release. |
151 | that has been installed using the new release. |
| 144 | </p> |
152 | </p> |
| 145 | |
153 | |
| 146 | </body> |
154 | </body> |
| … | |
… | |
| 148 | <section> |
156 | <section> |
| 149 | <title>Releases with profile changes</title> |
157 | <title>Releases with profile changes</title> |
| 150 | <body> |
158 | <body> |
| 151 | |
159 | |
| 152 | <p> |
160 | <p> |
| 153 | If a release introduces a new profile, you have the choice to migrate to the |
161 | If a release (such as 2007.0 for x86) introduces a new profile, you have the |
| 154 | new profile. |
162 | choice to migrate to the new profile. |
| 155 | </p> |
|
|
| 156 | |
|
|
| 157 | <p> |
163 | </p> |
|
|
164 | |
|
|
165 | <p> |
| 158 | Naturally, you are not forced to do so, you can continue to use the old profile |
166 | Naturally, you are not forced to do so, and you can continue to use the old |
| 159 | and just update your packages |
167 | profile and just update your packages |
| 160 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=2">as explained in |
168 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">as explained |
| 161 | the Gentoo Handbook</uri> (or you may want to not update your system at all). |
169 | in the Gentoo Handbook</uri>. |
| 162 | </p> |
|
|
| 163 | |
|
|
| 164 | <p> |
170 | </p> |
|
|
171 | |
|
|
172 | <p> |
| 165 | However, Gentoo strongly recommends a migration if your profile becomes |
173 | However, Gentoo strongly recommends updating your profile if it becomes |
| 166 | deprecated and is no more supported by Gentoo developers, that is to say that |
174 | deprecated. When this happens, it means that Gentoo developers no longer |
| 167 | your profile is not listed anymore in the table below. |
175 | plan on supporting it. |
| 168 | </p> |
176 | </p> |
| 169 | |
177 | |
| 170 | <p> |
178 | <p> |
| 171 | If you decide to migrate to the new profile, then you will have to manually |
179 | If you decide to migrate to the new profile, then you will have to manually |
| 172 | perform some actions. Those actions may vary a lot from release to release, it |
180 | perform the update. The way you update may vary significantly from release |
| 173 | depends on how deep the modifications introduced in the new profile are. |
181 | to release; it depends on how deep the modifications introduced in the new |
|
|
182 | profile are. |
| 174 | </p> |
183 | </p> |
| 175 | |
184 | |
| 176 | <p> |
185 | <p> |
| 177 | In the simplest case you only have to change the <path>/etc/make.profile</path> |
186 | In the simplest case you only have to change the <path>/etc/make.profile</path> |
| 178 | link, in the worst case you may have to recompile your system from scratch |
187 | symlink, in the worst case you may have to recompile your system from scratch |
| 179 | while doing some voodoo stuff. In every case we will publish the instructions |
188 | while doing a neat voodoo dance. Migration is usually covered in the release |
| 180 | for the migration as part of the release. You can find these instructions also |
189 | notes. You can also find <uri link="#instructions">instructions</uri> at the |
| 181 | at the end of this guide. |
190 | end of this guide. |
| 182 | </p> |
191 | </p> |
| 183 | |
192 | |
| 184 | </body> |
193 | </body> |
| 185 | </section> |
194 | </section> |
| 186 | <section> |
195 | <section> |
| 187 | <title>Supported profiles</title> |
196 | <title>Supported profiles</title> |
| 188 | <body> |
197 | <body> |
| 189 | |
198 | |
| 190 | <p> |
199 | <p> |
| 191 | The following profiles are officially supported by Gentoo developers: |
200 | You can view the list of profiles on your architecture officially supported by |
|
|
201 | Gentoo developers when you <c>emerge eselect</c> and then run the following |
|
|
202 | command: |
|
|
203 | </p> |
|
|
204 | |
|
|
205 | <pre caption="Viewing supported profiles"> |
|
|
206 | # <i>eselect profile list</i> |
|
|
207 | </pre> |
|
|
208 | |
|
|
209 | </body> |
|
|
210 | </section> |
|
|
211 | </chapter> |
|
|
212 | |
|
|
213 | <chapter id="instructions"> |
|
|
214 | <title>Profile updating instructions</title> |
|
|
215 | <section id="general"> |
|
|
216 | <title>General instructions</title> |
|
|
217 | <body> |
|
|
218 | |
|
|
219 | <impo> |
|
|
220 | Make sure your Portage is updated before performing any profile changes. |
|
|
221 | </impo> |
|
|
222 | |
|
|
223 | <p> |
|
|
224 | First, run <c>emerge eselect</c>. The <c>eselect</c> utility will let you view |
|
|
225 | and select profiles easily, without needing to create or remove symlinks by |
|
|
226 | hand. |
|
|
227 | </p> |
|
|
228 | |
|
|
229 | <pre caption="Profile selection with eselect"> |
|
|
230 | <comment>(View available profiles)</comment> |
|
|
231 | # <i>eselect profile list</i> |
|
|
232 | |
|
|
233 | <comment>(Select the number of your desired profile from the list)</comment> |
|
|
234 | # <i>eselect profile set <number></i> |
|
|
235 | </pre> |
|
|
236 | |
|
|
237 | <p> |
|
|
238 | If you'd still prefer to change profiles manually, then simply do the following: |
|
|
239 | </p> |
|
|
240 | |
|
|
241 | <pre caption="Changing profiles manually"> |
|
|
242 | # <i>rm /etc/make.profile</i> |
|
|
243 | # <i>ln -s ../usr/portage/profiles/</i><selected profile><i> /etc/make.profile</i> |
|
|
244 | </pre> |
|
|
245 | |
|
|
246 | <note> |
|
|
247 | There are <b>desktop</b> and <b>server</b> subprofiles for most architectures. |
|
|
248 | Examine these profiles carefully, as they may serve your needs better than the |
|
|
249 | extremely minimal default profiles. |
|
|
250 | </note> |
|
|
251 | |
|
|
252 | </body> |
|
|
253 | </section> |
|
|
254 | <section> |
|
|
255 | <title>Updating to 2007.0 or 2006.1</title> |
|
|
256 | <body> |
|
|
257 | |
|
|
258 | <p> |
|
|
259 | If you intend to upgrade to these profiles, you should be aware that they expect |
|
|
260 | the system to be set to a Unicode locale by default; specifically that |
|
|
261 | UNICODE="yes" is set in <path>/etc/rc.conf</path>. For this to work, you must |
|
|
262 | have created a Unicode locale for your system to use. Please read our <uri |
|
|
263 | link="/doc/en/utf-8.xml">UTF-8 guide</uri> to learn how to create the proper |
|
|
264 | locale. |
|
|
265 | </p> |
|
|
266 | |
|
|
267 | <p> |
|
|
268 | Alternatively, if you do not wish to set a locale, you should specify |
|
|
269 | UNICODE="no" in <path>/etc/rc.conf</path>, and re-emerge <c>baselayout</c> (or |
|
|
270 | wait until your next <c>baselayout</c> update) with the <c>-unicode</c> USE |
|
|
271 | flag. You can set <c>-unicode</c> just for <c>baselayout</c>, or you can set it |
|
|
272 | globally for all packages by adding it to your USE variable in |
|
|
273 | <path>/etc/make.conf</path>. |
|
|
274 | </p> |
|
|
275 | |
|
|
276 | <pre caption="Optional: removing Unicode support"> |
|
|
277 | <comment>(To remove Unicode support just for baselayout)</comment> |
|
|
278 | # <i>echo "sys-apps/baselayout -unicode" >> /etc/portage/package.use</i> |
|
|
279 | # <i>emerge -a baselayout</i> |
|
|
280 | |
|
|
281 | <comment>(To remove Unicode support from your whole system)</comment> |
|
|
282 | # <i>nano -w /etc/make.conf</i> |
|
|
283 | USE="-unicode" |
|
|
284 | # <i>emerge -a baselayout</i> |
|
|
285 | </pre> |
|
|
286 | |
|
|
287 | <note> |
|
|
288 | If you are updating to a 2007.0 profile on the Sparc architecture, then you will |
|
|
289 | need to follow the <uri link="/doc/en/gcc-upgrading.xml">GCC Upgrading |
|
|
290 | Guide</uri>, as <c>gcc-4</c> is the default compiler. |
|
|
291 | </note> |
|
|
292 | |
|
|
293 | <p> |
|
|
294 | Finally, follow the <uri link="#general">general instructions</uri> for updating |
|
|
295 | your profile. |
|
|
296 | </p> |
|
|
297 | |
|
|
298 | </body> |
|
|
299 | </section> |
|
|
300 | <section> |
|
|
301 | <title>Updating to 2006.0</title> |
|
|
302 | <body> |
|
|
303 | |
|
|
304 | <p> |
|
|
305 | To switch to the 2006.0 profile, point the <path>/etc/make.profile</path> |
|
|
306 | symlink to the new location. Make sure your Portage is updated before you |
|
|
307 | change your profile. |
|
|
308 | </p> |
|
|
309 | |
|
|
310 | <pre caption="Changing to a 2006.0 profile"> |
|
|
311 | # <i>rm /etc/make.profile</i> |
|
|
312 | # <i>ln -s ../usr/portage/profiles/</i><selected profile><i> /etc/make.profile</i> |
|
|
313 | </pre> |
|
|
314 | |
|
|
315 | <p> |
|
|
316 | <b>alpha</b> - Users that use a 2.4 kernel or don't want to use NPTL should use |
|
|
317 | the default-linux/alpha/no-nptl profile. More information is available in <uri |
|
|
318 | link="/proj/en/releng/release/2006.0/alpha-release-notes.xml">the alpha release |
|
|
319 | notes</uri>. |
|
|
320 | </p> |
|
|
321 | |
|
|
322 | <p> |
|
|
323 | <b>ppc</b> - The merge of the ppc32 and ppc64 profiles went forward. The ppc32 |
|
|
324 | profile has been changed in a way that offers a minimalistic generic profile |
|
|
325 | for all purposes, located in default-linux/ppc/ppc32. The release-dependent |
|
|
326 | profile is optimized for desktop-usage and located in |
|
|
327 | default-linux/ppc/ppc32/2006.0. There are some subprofiles available for G3 and |
|
|
328 | G4 processors, and G3/Pegasos and G4/Pegasos for the Pegasos Open Desktop |
|
|
329 | Workstation. Make sure you choose the correct subprofile for your system when |
|
|
330 | migrating to a 2006.0 profile. |
|
|
331 | </p> |
|
|
332 | |
|
|
333 | <p> |
|
|
334 | <b>sparc</b> - Upgrading to the <b>2.4</b>-kernel based 2006.0/2.4 profile |
|
|
335 | requires manual user intervention (unmerging java stuff) and an <c>emerge -e |
|
|
336 | world</c> because of the <uri link="/doc/en/gcc-upgrading.xml">gcc |
|
|
337 | upgrade</uri>.<br/> |
|
|
338 | Upgrading to the <b>2.6</b>-kernel based 2006.0 profile which is not considered |
|
|
339 | stable also requires an entry in <path>/etc/portage/package.unmask</path> to |
|
|
340 | umask a 2.6 version of <c>gentoo-sources</c> and a full rebuild. |
|
|
341 | </p> |
|
|
342 | |
|
|
343 | <p> |
|
|
344 | <b>All other archs</b> - There are no fundamental changes in this profile. No |
|
|
345 | specific action needs to be performed. |
|
|
346 | </p> |
|
|
347 | |
|
|
348 | </body> |
|
|
349 | </section> |
|
|
350 | <section> |
|
|
351 | <title>Updating to 2005.1</title> |
|
|
352 | <body> |
|
|
353 | |
|
|
354 | <p> |
|
|
355 | To switch to the 2005.1 profile, point the <path>/etc/make.profile</path> |
|
|
356 | symlink to the new location. Make sure your Portage is updated before you |
|
|
357 | change your profile. |
|
|
358 | </p> |
|
|
359 | |
|
|
360 | <pre caption="Changing to a 2005.1 profile"> |
|
|
361 | # <i>rm /etc/make.profile</i> |
|
|
362 | # <i>ln -s ../usr/portage/profiles/</i><selected profile><i> /etc/make.profile</i> |
|
|
363 | </pre> |
|
|
364 | |
|
|
365 | <p> |
|
|
366 | <b>All archs</b> - There are no fundamental changes in this profile. No |
|
|
367 | specific action needs to be performed. |
|
|
368 | </p> |
|
|
369 | |
|
|
370 | <p> |
|
|
371 | <b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged |
|
|
372 | and a number of subprofiles for specific subarchitectures were created. Make |
|
|
373 | sure you choose the correct subprofile for your system when migrating to a |
|
|
374 | 2005.1 profile. |
|
|
375 | </p> |
|
|
376 | |
|
|
377 | </body> |
|
|
378 | </section> |
|
|
379 | <section> |
|
|
380 | <title>Updating to 2005.0</title> |
|
|
381 | <body> |
|
|
382 | |
|
|
383 | <p> |
|
|
384 | With the introduction of 2005.0, several architectures have decided to define |
|
|
385 | additional profiles. Make sure you read the description of said profiles before |
|
|
386 | you decide to migrate to one of them. Most architectures now also default to the |
|
|
387 | 2.6 kernel tree where 2.4 was chosen previously. |
|
|
388 | </p> |
|
|
389 | |
|
|
390 | <p> |
|
|
391 | Some architectures require a bit more actions to be completed in order to |
|
|
392 | convert from one profile to another. If that is the case, the step-by-step |
|
|
393 | guides are linked from the table. |
| 192 | </p> |
394 | </p> |
| 193 | |
395 | |
| 194 | <table> |
396 | <table> |
| 195 | <tr> |
397 | <tr> |
| 196 | <th>Architecture</th> |
398 | <th>Profile</th> |
| 197 | <th>Most recent profile</th> |
399 | <th>Description</th> |
| 198 | <th>Other supported profiles</th> |
400 | <th>Specific Upgrade Guide</th> |
| 199 | </tr> |
|
|
| 200 | <tr> |
401 | </tr> |
| 201 | <th>x86</th> |
|
|
| 202 | <ti>2004.0</ti> |
|
|
| 203 | <ti>1.4</ti> |
|
|
| 204 | </tr> |
402 | <tr> |
|
|
403 | <ti>default-linux/alpha/2005.0</ti> |
|
|
404 | <ti>Default Alpha 2005.0 profile for 2.6 kernels</ti> |
|
|
405 | <ti></ti> |
| 205 | <tr> |
406 | </tr> |
| 206 | <th>hardened-x86</th> |
|
|
| 207 | <ti>2004.0</ti> |
|
|
| 208 | <ti></ti> |
|
|
| 209 | </tr> |
407 | <tr> |
|
|
408 | <ti>default-linux/alpha/2005.0/2.4</ti> |
|
|
409 | <ti>Alpha 2005.0 profile for 2.4 kernels</ti> |
|
|
410 | <ti></ti> |
| 210 | <tr> |
411 | </tr> |
| 211 | <th>amd64</th> |
|
|
| 212 | <ti>2004.0</ti> |
|
|
| 213 | <ti></ti> |
|
|
| 214 | </tr> |
412 | <tr> |
|
|
413 | <ti>default-linux/amd64/2005.0</ti> |
|
|
414 | <ti>Default AMD64 2005.0 profile for 2.6 kernels</ti> |
|
|
415 | <ti></ti> |
| 215 | <tr> |
416 | </tr> |
| 216 | <th>ppc</th> |
|
|
| 217 | <ti>2004.0</ti> |
|
|
| 218 | <ti>1.4</ti> |
|
|
| 219 | </tr> |
417 | <tr> |
|
|
418 | <ti>default-linux/amd64/2005.0/no-multilib</ti> |
|
|
419 | <ti>AMD64 2005.0 profile for multilib-disabled system installations</ti> |
|
|
420 | <ti></ti> |
| 220 | <tr> |
421 | </tr> |
| 221 | <th>sparc</th> |
|
|
| 222 | <ti>2004.0</ti> |
|
|
| 223 | <ti>1.4</ti> |
|
|
| 224 | </tr> |
422 | <tr> |
|
|
423 | <ti>default-linux/arm/2005.0</ti> |
|
|
424 | <ti>Default ARM 2005.0 profile for 2.6 kernels</ti> |
|
|
425 | <ti></ti> |
| 225 | <tr> |
426 | </tr> |
| 226 | <th>mips</th> |
|
|
| 227 | <ti>2004.0</ti> |
|
|
| 228 | <ti>1.4</ti> |
|
|
| 229 | </tr> |
427 | <tr> |
|
|
428 | <ti>default-linux/hppa/2005.0</ti> |
|
|
429 | <ti>Default HPPA 2005.0 profile for 2.6 kernels</ti> |
|
|
430 | <ti></ti> |
| 230 | <tr> |
431 | </tr> |
| 231 | <th>hppa</th> |
432 | <tr> |
|
|
433 | <ti>default-linux/hppa/2005.0/2.4</ti> |
|
|
434 | <ti>HPPA 2005.0 profile for 2.4 kernels</ti> |
| 232 | <ti>2004.0</ti> |
435 | <ti></ti> |
|
|
436 | </tr> |
|
|
437 | <tr> |
|
|
438 | <ti>default-linux/mips/2005.0</ti> |
|
|
439 | <ti>Default MIPS 2005.0 profile</ti> |
|
|
440 | <ti></ti> |
|
|
441 | </tr> |
|
|
442 | <tr> |
|
|
443 | <ti>default-linux/mips/cobalt/2005.0</ti> |
|
|
444 | <ti>Cobalt specific MIPS 2005.0 profile</ti> |
|
|
445 | <ti></ti> |
|
|
446 | </tr> |
|
|
447 | <tr> |
|
|
448 | <ti>default-linux/mips/mips64/n32/2005.0</ti> |
|
|
449 | <ti>2005.0 profile for n32-supporting MIPS platforms</ti> |
|
|
450 | <ti></ti> |
|
|
451 | </tr> |
|
|
452 | <tr> |
|
|
453 | <ti>default-linux/mips/mips64/ip28/2005.0</ti> |
|
|
454 | <ti>Indigo2 Impact specific 64-bit 2005.0 profile</ti> |
|
|
455 | <ti></ti> |
|
|
456 | </tr> |
|
|
457 | <tr> |
|
|
458 | <ti>default-linux/mips/mips64/2005.0</ti> |
|
|
459 | <ti>64-bit MIPS 2005.0 profile</ti> |
|
|
460 | <ti></ti> |
|
|
461 | </tr> |
|
|
462 | <tr> |
|
|
463 | <ti>default-linux/ppc/2005.0</ti> |
|
|
464 | <ti>Default PPC 2005.0 profile for 2.6 kernels</ti> |
|
|
465 | <ti></ti> |
|
|
466 | </tr> |
|
|
467 | <tr> |
|
|
468 | <ti>default-linux/ppc64/2005.0</ti> |
|
|
469 | <ti>Default PPC64 2005.0 profile for 2.6 kernels</ti> |
|
|
470 | <ti></ti> |
|
|
471 | </tr> |
|
|
472 | <tr> |
|
|
473 | <ti>default-linux/s390/2005.0</ti> |
|
|
474 | <ti>Default S390 2005.0 profile</ti> |
|
|
475 | <ti></ti> |
|
|
476 | </tr> |
|
|
477 | <tr> |
|
|
478 | <ti>default-linux/sparc/sparc32/2005.0</ti> |
|
|
479 | <ti>Default Sparc 32-bit 2005.0 profile</ti> |
|
|
480 | <ti></ti> |
|
|
481 | </tr> |
|
|
482 | <!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm |
|
|
483 | No subprofiles for sparc |
|
|
484 | <tr> |
|
|
485 | <ti>default-linux/sparc/sparc32/2005.0/2.6</ti> |
|
|
486 | <ti>Sparc 32-bit 2005.0 profile for 2.6 kernels</ti> |
|
|
487 | <ti></ti> |
|
|
488 | </tr> |
|
|
489 | --> |
|
|
490 | <tr> |
|
|
491 | <ti>default-linux/sparc/sparc64/2005.0</ti> |
|
|
492 | <ti>Default Sparc 64-bit 2005.0 profile</ti> |
|
|
493 | <ti></ti> |
|
|
494 | </tr> |
|
|
495 | <!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm |
|
|
496 | No subprofiles for sparc |
|
|
497 | <tr> |
|
|
498 | <ti>default-linux/sparc/sparc64/2005.0/2.6</ti> |
|
|
499 | <ti>Sparc 64-bit 2005.0 profile for 2.6 kernels</ti> |
|
|
500 | <ti></ti> |
|
|
501 | </tr> |
|
|
502 | --> |
|
|
503 | <tr> |
|
|
504 | <ti>default-linux/x86/2005.0</ti> |
|
|
505 | <ti>Default x86 2005.0 profile for 2.6 kernels</ti> |
|
|
506 | <ti></ti> |
|
|
507 | </tr> |
|
|
508 | <tr> |
|
|
509 | <ti>default-linux/x86/2005.0/2.4</ti> |
|
|
510 | <ti>x86 2005.0 profile for 2.4 kernels</ti> |
| 233 | <ti></ti> |
511 | <ti></ti> |
| 234 | </tr> |
512 | </tr> |
| 235 | </table> |
513 | </table> |
| 236 | |
514 | |
| 237 | </body> |
515 | <p> |
| 238 | </section> |
516 | To switch to the selected profile, point the <path>/etc/make.profile</path> |
| 239 | </chapter> |
517 | symlink to the new location. Make sure your Portage is updated before you change |
|
|
518 | your profile! |
|
|
519 | </p> |
| 240 | |
520 | |
| 241 | <chapter> |
521 | <pre caption="Changing to a 2005.0 profile"> |
| 242 | <title>Profile updating instructions</title> |
522 | # <i>rm /etc/make.profile</i> |
|
|
523 | # <i>ln -s ../usr/portage/profiles/</i><selected profile><i> /etc/make.profile</i> |
|
|
524 | </pre> |
|
|
525 | |
|
|
526 | <p> |
|
|
527 | If you are running a Linux 2.4-based system but want to migrate to a 2.6-based |
|
|
528 | kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo |
|
|
529 | Linux 2.6 Migration Guide</uri>. |
|
|
530 | </p> |
|
|
531 | |
|
|
532 | </body> |
| 243 | <section> |
533 | </section> |
| 244 | <title>Updating from 1.4 to 2004.0 (all archs)</title> |
534 | <section> |
|
|
535 | <title>Updating to 2004.3</title> |
| 245 | <body> |
536 | <body> |
| 246 | |
537 | |
| 247 | <p> |
|
|
| 248 | There are no fundamental changes between 1.4 and 2004.0 profiles. Just point |
|
|
| 249 | the <path>/etc/make.profile</path> link to the new location: |
|
|
| 250 | </p> |
538 | <p> |
|
|
539 | With the introduction of the 2004.3 profiles, users are not going to see huge |
|
|
540 | modifications of their systems (see below for details). However, Gentoo |
|
|
541 | developers decided to push out this new profile and to deprecate quite a few of |
|
|
542 | the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the |
|
|
543 | profiles that follow the new layout of the <path>/usr/portage/profiles</path> |
|
|
544 | directory, for instance |
|
|
545 | <path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by |
|
|
546 | Portage 2.0.51 or later). |
|
|
547 | </p> |
| 251 | |
548 | |
|
|
549 | <p> |
|
|
550 | To switch to the 2004.3 profile, point the <path>/etc/make.profile</path> |
|
|
551 | symlink to the new location: |
|
|
552 | </p> |
|
|
553 | |
|
|
554 | <warn> |
|
|
555 | Don't forget to upgrade Portage <e>before</e> you change your profile!!! |
|
|
556 | </warn> |
|
|
557 | |
| 252 | <pre caption="Updating the /etc/make.profile link"> |
558 | <pre caption="Updating the /etc/make.profile symlink"> |
|
|
559 | <comment>substitute <arch> with your arch</comment> |
| 253 | # <i>rm /etc/make.profile</i> |
560 | # <i>rm /etc/make.profile</i> |
|
|
561 | # <i>ln -s ../usr/portage/profiles/default-linux/<arch>/2004.3 /etc/make.profile</i> |
|
|
562 | </pre> |
|
|
563 | |
|
|
564 | <p> |
|
|
565 | <b>All archs</b> - As said above, there are no big changes introduced in this |
|
|
566 | profile. However, it should be noted that <c>sys-apps/slocate</c> and |
|
|
567 | <c>net-misc/dhcpcd</c> are no longer considered system packages. This means |
|
|
568 | that if you run <c>emerge --depclean</c>, Portage will try to remove them from |
|
|
569 | your system. If you need any of those packages, add them to |
|
|
570 | <path>/var/lib/portage/world</path> after the profile switch, or manually |
|
|
571 | emerge them. |
|
|
572 | </p> |
|
|
573 | |
|
|
574 | <p> |
|
|
575 | <b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of |
|
|
576 | <c>sys-fs/devfs</c> for newly installed machines. This has no |
|
|
577 | effect on already installed machines, though. |
|
|
578 | </p> |
|
|
579 | |
|
|
580 | </body> |
|
|
581 | </section> |
|
|
582 | <section> |
|
|
583 | <title>Updating Portage to Support Cascading Profiles</title> |
|
|
584 | <body> |
|
|
585 | |
|
|
586 | <p> |
|
|
587 | Although this section does not seem to integrate well in this upgrading guide, |
|
|
588 | it is quite important. Any profile listed above this section requires a Portage |
|
|
589 | version that supports cascading profiles. However, some obsoleted profiles don't |
|
|
590 | allow the user to upgrade Portage or the user is using a profile that isn't |
|
|
591 | available anymore - any attempt to upgrade Portage will result in a failure. |
|
|
592 | </p> |
|
|
593 | |
|
|
594 | <p> |
|
|
595 | To work around this problem, users can set a temporary symbolic link to the |
|
|
596 | <e>obsolete</e> profile, allowing them to upgrade their Portage after which |
|
|
597 | they can continue with the upgrade procedure set forth in this guide. Please |
|
|
598 | substitute <c><arch></c> with your respective architecture: |
|
|
599 | </p> |
|
|
600 | |
|
|
601 | <pre caption="Updating Portage through the obsolete profile"> |
|
|
602 | # <i>rm /etc/make.profile</i> |
|
|
603 | # <i>cd /etc</i> |
|
|
604 | # <i>ln -sf ../usr/portage/profiles/obsolete/<arch> make.profile</i> |
|
|
605 | # <i>emerge -n '>=sys-apps/portage-2.0.51'</i> |
|
|
606 | </pre> |
|
|
607 | |
|
|
608 | </body> |
|
|
609 | </section> |
|
|
610 | <section> |
|
|
611 | <title>Updating to 2004.2</title> |
|
|
612 | <body> |
|
|
613 | |
|
|
614 | <p> |
|
|
615 | To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> |
|
|
616 | symlink to the new location: |
|
|
617 | </p> |
|
|
618 | |
|
|
619 | <warn> |
|
|
620 | Don't forget to upgrade Portage <e>before</e> you change your profile!!! |
|
|
621 | </warn> |
|
|
622 | |
|
|
623 | <pre caption="Updating the /etc/make.profile symlink"> |
|
|
624 | <comment>substitute <arch> with your arch</comment> |
|
|
625 | # <i>rm /etc/make.profile</i> |
|
|
626 | # <i>ln -s ../usr/portage/profiles/default-linux/<arch>/2004.2 /etc/make.profile</i> |
|
|
627 | </pre> |
|
|
628 | |
|
|
629 | <p> |
|
|
630 | <b>x86</b> - This profile changes the default X11 implementation from |
|
|
631 | <c>x11-base/xfree</c> to <c>x11-base/xorg-x11</c>. This change only touches |
|
|
632 | the <e>default</e> value, and is only relevant for those who have not installed |
|
|
633 | an X server yet. If you already have one installed, then it will not affect |
|
|
634 | you at all; you are free to switch from one X server to the other exactly as |
|
|
635 | before. |
|
|
636 | </p> |
|
|
637 | |
|
|
638 | <p> |
|
|
639 | <b>amd64</b> - There are no fundamental changes from previous profiles, no |
|
|
640 | specific action needs to be performed. |
|
|
641 | </p> |
|
|
642 | |
|
|
643 | </body> |
|
|
644 | </section> |
|
|
645 | <section> |
|
|
646 | <title>Updating to 2004.0</title> |
|
|
647 | <body> |
|
|
648 | |
|
|
649 | <p> |
|
|
650 | To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> |
|
|
651 | symlink to the new location: |
|
|
652 | </p> |
|
|
653 | |
|
|
654 | <pre caption="Updating the /etc/make.profile symlink"> |
|
|
655 | <comment>substitute <arch> with your arch</comment> |
|
|
656 | # <i>rm /etc/make.profile</i> |
| 254 | # <i>ln -s ../usr/portage/profiles/default-x86-2004.0 /etc/make.profile</i> |
657 | # <i>ln -s ../usr/portage/profiles/default-<arch>-2004.0 /etc/make.profile</i> |
|
|
658 | </pre> |
|
|
659 | |
|
|
660 | <p> |
|
|
661 | <b>All archs</b> - There are no fundamental changes from previous profiles, no |
|
|
662 | specific action needs to be performed. |
| 255 | </pre> |
663 | </p> |
| 256 | |
664 | |
| 257 | </body> |
665 | </body> |
| 258 | </section> |
666 | </section> |
| 259 | <section> |
667 | <section> |
| 260 | <title>Updating from profiles older than 1.4 to 1.4</title> |
668 | <title>Updating from profiles older than 1.4 to 1.4</title> |
| … | |
… | |
| 268 | </body> |
676 | </body> |
| 269 | </section> |
677 | </section> |
| 270 | </chapter> |
678 | </chapter> |
| 271 | |
679 | |
| 272 | </guide> |
680 | </guide> |
| 273 | |
|
|
Parent Directory
| 
Revision Log
| 
Patch