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