| 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.29 2006/02/12 18:59:02 rane 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> |
| 13 | This document explains how new Gentoo releases affect existing installs. |
13 | This 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.5 --> |
| 18 | <license/> |
18 | <license/> |
| 19 | |
19 | |
| 20 | <version>2.3</version> |
20 | <version>2.2</version> |
| 21 | <date>September 25, 2004</date> |
21 | <date>2006-02-12</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> |
| … | |
… | |
| 37 | <p> |
37 | <p> |
| 38 | You know (being a Gentoo user after all) that this process is extremely |
38 | 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 |
39 | 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 |
40 | 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 |
41 | 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 |
42 | 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, |
43 | suited than Gentoo to satisfy these kind of demanding users. From the |
| 44 | Gentoo was designed around the concept of fast, incremental updates. |
44 | beginning, Gentoo was designed around the concept of fast, incremental |
| 45 | </p> |
45 | updates. |
| 46 | |
|
|
| 47 | <p> |
46 | </p> |
|
|
47 | |
|
|
48 | <p> |
| 48 | Ideally, you install once and then do not to bother with releases: |
49 | Ideally, you install once and never bother with releases: just follow the |
| 49 | just follow the instructions in |
50 | instructions in <uri |
| 50 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">A Portage |
51 | link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">A Portage |
| 51 | Introduction</uri> in the |
52 | 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 |
53 | 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 |
54 | 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. |
55 | to be done manually. |
| 55 | </p> |
56 | </p> |
| 56 | |
57 | |
| 57 | </body> |
58 | </body> |
| 58 | </section> |
59 | </section> |
| 59 | <section> |
60 | <section> |
| … | |
… | |
| 66 | There are various reasons: |
67 | There are various reasons: |
| 67 | </p> |
68 | </p> |
| 68 | |
69 | |
| 69 | <ul> |
70 | <ul> |
| 70 | <li> |
71 | <li> |
| 71 | A new release means new LiveCDs with bugfixes and more features. |
72 | A new release means new Installation CDs with bugfixes and more features. |
| 72 | </li> |
73 | </li> |
| 73 | <li> |
74 | <li> |
| 74 | A new release provides an updated set of GRP packages, so that users that |
75 | 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 |
76 | choose "the fast way" to install (stage3 + precompiled packages) end up |
| 76 | with a system that is not outdated. |
77 | with a system that is not outdated. |
| 77 | </li> |
78 | </li> |
| 78 | <li> |
79 | <li> |
| 79 | Finally, a new release may, from time to time, implement some features that |
80 | Finally, a new release may, from time to time, implement some features that |
| 80 | are incompatible with previous releases. |
81 | are incompatible with previous releases. |
| … | |
… | |
| 87 | that it provides a new <e>profile</e>. |
88 | that it provides a new <e>profile</e>. |
| 88 | </p> |
89 | </p> |
| 89 | |
90 | |
| 90 | <p> |
91 | <p> |
| 91 | A <e>profile</e> is a set of configuration files, stored in a subdirectory of |
92 | 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 |
93 | <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 |
94 | 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. |
95 | mapping for virtual packages, and the architecture on which the system is running. |
| 95 | </p> |
96 | </p> |
| 96 | |
97 | |
| 97 | <p> |
98 | <p> |
| 98 | The profile in use is determined by the symbolic link |
99 | The profile in use is determined by the symbolic link |
| 99 | <path>/etc/make.profile</path>, which points to a subdirectory of |
100 | <path>/etc/make.profile</path>, which points to a subdirectory of |
| 100 | <path>/usr/portage/profiles</path> which holds the profile files. For instance, |
101 | <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> |
102 | instance, the default x86 2005.1 profile can be found |
| 102 | (old-style location) or at <path>/usr/portage/profiles/default-linux/x86/2004.2</path> (new-style |
103 | at <path>/usr/portage/profiles/default-linux/x86/2005.1</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 |
104 | 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 |
105 | are therefore shared by different subprofiles). This is why we call these |
| 105 | by different subprofiles). |
106 | <e>cascaded profiles</e>. |
| 106 | </p> |
107 | </p> |
| 107 | |
108 | |
| 108 | <p> |
109 | <p> |
| 109 | Profiles obsoleted by new ones are kept in <path>/usr/portage/profiles</path> |
110 | 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 |
111 | 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 |
112 | 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 |
113 | 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. |
114 | to"; portage uses this information to automatically warn you when you should |
| 114 | </p> |
115 | update to a new profile. |
| 115 | |
|
|
| 116 | <p> |
116 | </p> |
|
|
117 | |
|
|
118 | <p> |
| 117 | There are various reasons that a new profile may be created: the release of new |
119 | 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>) |
120 | 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 |
121 | <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 |
122 | 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). |
123 | system-wide settings. |
| 122 | </p> |
124 | </p> |
| 123 | |
125 | |
| 124 | </body> |
126 | </body> |
| 125 | </section> |
127 | </section> |
| 126 | </chapter> |
128 | </chapter> |
| … | |
… | |
| 130 | <section> |
132 | <section> |
| 131 | <title>Releases without profile changes</title> |
133 | <title>Releases without profile changes</title> |
| 132 | <body> |
134 | <body> |
| 133 | |
135 | |
| 134 | <p> |
136 | <p> |
| 135 | If a new Gentoo release is announced that does not include a new profile (such |
137 | 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 |
138 | then you can safely pretend that it never happened :). |
| 137 | happened :). |
|
|
| 138 | </p> |
139 | </p> |
| 139 | |
140 | |
| 140 | <p> |
141 | <p> |
| 141 | If you update your installed packages |
142 | If you update your installed packages |
| 142 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">as explained in |
143 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">as explained in |
| … | |
… | |
| 149 | <section> |
150 | <section> |
| 150 | <title>Releases with profile changes</title> |
151 | <title>Releases with profile changes</title> |
| 151 | <body> |
152 | <body> |
| 152 | |
153 | |
| 153 | <p> |
154 | <p> |
| 154 | If a release introduces a new profile, you have the choice to migrate to the |
155 | If a release (such as 2005.1 for x86) introduces a new profile, you have the |
| 155 | new profile. |
156 | choice to migrate to the new profile. |
| 156 | </p> |
|
|
| 157 | |
|
|
| 158 | <p> |
157 | </p> |
|
|
158 | |
|
|
159 | <p> |
| 159 | Naturally, you are not forced to do so, and you can continue to use the old profile |
160 | Naturally, you are not forced to do so, and you can continue to use the old |
| 160 | and just update your packages |
161 | profile and just update your packages |
| 161 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">as explained in |
162 | <uri link="/doc/en/handbook/handbook-x86.xml?part=2&chap=1">as explained |
| 162 | the Gentoo Handbook</uri>. |
163 | in the Gentoo Handbook</uri>. |
| 163 | </p> |
|
|
| 164 | |
|
|
| 165 | <p> |
164 | </p> |
|
|
165 | |
|
|
166 | <p> |
| 166 | However, Gentoo strongly recommends updating your profile if it becomes deprecated. |
167 | 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. |
168 | 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. |
169 | plan on supporting it. Using the table below, you can quickly check to |
|
|
170 | see what profiles are currently supported. |
| 169 | </p> |
171 | </p> |
| 170 | |
172 | |
| 171 | <p> |
173 | <p> |
| 172 | If you decide to migrate to the new profile, then you will have to manually |
174 | 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 |
175 | perform the update. The way you update may vary significantly from release |
| 174 | depends on how deep the modifications introduced in the new profile. |
176 | to release; it depends on how deep the modifications introduced in the new |
|
|
177 | profile are. |
| 175 | </p> |
178 | </p> |
| 176 | |
179 | |
| 177 | <p> |
180 | <p> |
| 178 | In the simplest case you only have to change the <path>/etc/make.profile</path> |
181 | 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 |
182 | 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 |
183 | 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. |
184 | notes. You can also find <uri link="#instructions">instructions</uri> at the |
|
|
185 | end of this guide. |
| 182 | </p> |
186 | </p> |
| 183 | |
187 | |
| 184 | </body> |
188 | </body> |
| 185 | </section> |
189 | </section> |
| 186 | <section> |
190 | <section> |
| … | |
… | |
| 192 | </p> |
196 | </p> |
| 193 | |
197 | |
| 194 | <table> |
198 | <table> |
| 195 | <tr> |
199 | <tr> |
| 196 | <th>Architecture</th> |
200 | <th>Architecture</th> |
| 197 | <th>Most recent profile</th> |
201 | <th>Most recent profiles</th> |
| 198 | <th>Other supported profiles</th> |
202 | <th>Other supported profiles</th> |
| 199 | </tr> |
203 | </tr> |
| 200 | <tr> |
204 | <tr> |
|
|
205 | <th>alpha</th> |
|
|
206 | <ti>2005.0, 2005.0/2.4</ti> |
|
|
207 | <ti></ti> |
|
|
208 | </tr> |
|
|
209 | <tr> |
| 201 | <th>arm</th> |
210 | <th>arm</th> |
| 202 | <ti>2004.0</ti> |
211 | <ti>2004.3</ti> |
| 203 | <ti></ti> |
212 | <ti></ti> |
| 204 | </tr> |
213 | </tr> |
| 205 | <tr> |
214 | <tr> |
| 206 | <th>amd64</th> |
215 | <th>amd64</th> |
|
|
216 | <ti>2005.1, 2005.1/no-multilib</ti> |
|
|
217 | <ti>2005.0, 2005.0/no-multilib, 2004.3</ti> |
|
|
218 | </tr> |
|
|
219 | <tr> |
|
|
220 | <th>hppa</th> |
|
|
221 | <ti>2005.0, 2005.0/2.4</ti> |
|
|
222 | <ti>2004.3, 2004.2</ti> |
|
|
223 | </tr> |
|
|
224 | <tr> |
|
|
225 | <th>ia64</th> |
|
|
226 | <ti>2005.0</ti> |
|
|
227 | <ti>2004.3</ti> |
|
|
228 | </tr> |
|
|
229 | <tr> |
|
|
230 | <th>ppc</th> |
|
|
231 | <ti>2005.1</ti> |
|
|
232 | <ti>2005.0, 2004.3, 2004.0</ti> |
|
|
233 | </tr> |
|
|
234 | <tr> |
|
|
235 | <th>mips</th> |
|
|
236 | <ti>2005.0</ti> |
| 207 | <ti>2004.2</ti> |
237 | <ti>2004.2</ti> |
|
|
238 | </tr> |
|
|
239 | <tr> |
|
|
240 | <th>s390</th> |
| 208 | <ti>2004.0</ti> |
241 | <ti>2004.3</ti> |
| 209 | </tr> |
|
|
| 210 | <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> |
242 | <ti></ti> |
| 229 | </tr> |
243 | </tr> |
| 230 | <tr> |
244 | <tr> |
| 231 | <th>sparc</th> |
245 | <th>sparc</th> |
|
|
246 | <ti>2005.1</ti> |
| 232 | <ti>2004.0</ti> |
247 | <ti>2005.0</ti> |
| 233 | <ti></ti> |
|
|
| 234 | </tr> |
|
|
| 235 | <tr> |
|
|
| 236 | <th>sparc64</th> |
|
|
| 237 | <ti>2004.0</ti> |
|
|
| 238 | <ti></ti> |
|
|
| 239 | </tr> |
248 | </tr> |
| 240 | <tr> |
249 | <tr> |
| 241 | <th>x86</th> |
250 | <th>x86</th> |
| 242 | <ti>2004.2</ti> |
251 | <ti>2005.1, 2005.1/2.4</ti> |
| 243 | <ti>2004.0, 1.4</ti> |
252 | <ti>2005.0, 2005.0/2.4</ti> |
| 244 | </tr> |
253 | </tr> |
| 245 | </table> |
254 | </table> |
| 246 | |
255 | |
| 247 | </body> |
256 | </body> |
| 248 | </section> |
257 | </section> |
| 249 | </chapter> |
258 | </chapter> |
| 250 | |
259 | |
| 251 | <chapter> |
260 | <chapter id="instructions"> |
| 252 | <title>Profile updating instructions</title> |
261 | <title>Profile updating instructions</title> |
| 253 | <section> |
262 | <section> |
|
|
263 | <title>Updating to 2005.1</title> |
|
|
264 | <body> |
|
|
265 | |
|
|
266 | <p> |
|
|
267 | To switch to the 2005.1 profile, point the <path>/etc/make.profile</path> |
|
|
268 | symlink to the new location. Make sure your Portage is updated before you |
|
|
269 | change your profile. |
|
|
270 | </p> |
|
|
271 | |
|
|
272 | <pre caption="Changing to a 2005.1 profile"> |
|
|
273 | # <i>rm /etc/make.profile</i> |
|
|
274 | # <i>ln -s ../usr/portage/profiles/</i><selected profile><i> /etc/make.profile</i> |
|
|
275 | </pre> |
|
|
276 | |
|
|
277 | <p> |
|
|
278 | <b>All archs</b> - There are no fundamental changes in this profile. No |
|
|
279 | specific action needs to be performed. |
|
|
280 | </p> |
|
|
281 | |
|
|
282 | <p> |
|
|
283 | <b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged |
|
|
284 | and a number of subprofiles for specific subarchitectures were created. Make |
|
|
285 | sure you choose the correct subprofile for your system when migrating to a |
|
|
286 | 2005.1 profile. |
|
|
287 | </p> |
|
|
288 | |
|
|
289 | </body> |
|
|
290 | </section> |
|
|
291 | <section> |
|
|
292 | <title>Updating to 2005.0</title> |
|
|
293 | <body> |
|
|
294 | |
|
|
295 | <p> |
|
|
296 | With the introduction of 2005.0, several architectures have decided to define |
|
|
297 | additional profiles. Make sure you read the description of said profiles before |
|
|
298 | you decide to migrate to one of them. Most architectures now also default to the |
|
|
299 | 2.6 kernel tree where 2.4 was chosen previously. |
|
|
300 | </p> |
|
|
301 | |
|
|
302 | <p> |
|
|
303 | Some architectures require a bit more actions to be completed in order to |
|
|
304 | convert from one profile to another. If that is the case, the step-by-step |
|
|
305 | guides are linked from the table. |
|
|
306 | </p> |
|
|
307 | |
|
|
308 | <table> |
|
|
309 | <tr> |
|
|
310 | <th>Profile</th> |
|
|
311 | <th>Description</th> |
|
|
312 | <th>Specific Upgrade Guide</th> |
|
|
313 | </tr> |
|
|
314 | <tr> |
|
|
315 | <ti>default-linux/alpha/2005.0</ti> |
|
|
316 | <ti>Default Alpha 2005.0 profile for 2.6 kernels</ti> |
|
|
317 | <ti></ti> |
|
|
318 | </tr> |
|
|
319 | <tr> |
|
|
320 | <ti>default-linux/alpha/2005.0/2.4</ti> |
|
|
321 | <ti>Alpha 2005.0 profile for 2.4 kernels</ti> |
|
|
322 | <ti></ti> |
|
|
323 | </tr> |
|
|
324 | <tr> |
|
|
325 | <ti>default-linux/amd64/2005.0</ti> |
|
|
326 | <ti>Default AMD64 2005.0 profile for 2.6 kernels</ti> |
|
|
327 | <ti></ti> |
|
|
328 | </tr> |
|
|
329 | <tr> |
|
|
330 | <ti>default-linux/amd64/2005.0/no-multilib</ti> |
|
|
331 | <ti>AMD64 2005.0 profile for multilib-disabled system installations</ti> |
|
|
332 | <ti></ti> |
|
|
333 | </tr> |
|
|
334 | <tr> |
|
|
335 | <ti>default-linux/arm/2005.0</ti> |
|
|
336 | <ti>Default ARM 2005.0 profile for 2.6 kernels</ti> |
|
|
337 | <ti></ti> |
|
|
338 | </tr> |
|
|
339 | <tr> |
|
|
340 | <ti>default-linux/hppa/2005.0</ti> |
|
|
341 | <ti>Default HPPA 2005.0 profile for 2.6 kernels</ti> |
|
|
342 | <ti></ti> |
|
|
343 | </tr> |
|
|
344 | <tr> |
|
|
345 | <ti>default-linux/hppa/2005.0/2.4</ti> |
|
|
346 | <ti>HPPA 2005.0 profile for 2.4 kernels</ti> |
|
|
347 | <ti></ti> |
|
|
348 | </tr> |
|
|
349 | <tr> |
|
|
350 | <ti>default-linux/mips/2005.0</ti> |
|
|
351 | <ti>Default MIPS 2005.0 profile</ti> |
|
|
352 | <ti></ti> |
|
|
353 | </tr> |
|
|
354 | <tr> |
|
|
355 | <ti>default-linux/mips/cobalt/2005.0</ti> |
|
|
356 | <ti>Cobalt specific MIPS 2005.0 profile</ti> |
|
|
357 | <ti></ti> |
|
|
358 | </tr> |
|
|
359 | <tr> |
|
|
360 | <ti>default-linux/mips/mips64/n32/2005.0</ti> |
|
|
361 | <ti>2005.0 profile for n32-supporting MIPS platforms</ti> |
|
|
362 | <ti></ti> |
|
|
363 | </tr> |
|
|
364 | <tr> |
|
|
365 | <ti>default-linux/mips/mips64/ip28/2005.0</ti> |
|
|
366 | <ti>Indigo2 Impact specific 64-bit 2005.0 profile</ti> |
|
|
367 | <ti></ti> |
|
|
368 | </tr> |
|
|
369 | <tr> |
|
|
370 | <ti>default-linux/mips/mips64/2005.0</ti> |
|
|
371 | <ti>64-bit MIPS 2005.0 profile</ti> |
|
|
372 | <ti></ti> |
|
|
373 | </tr> |
|
|
374 | <tr> |
|
|
375 | <ti>default-linux/ppc/2005.0</ti> |
|
|
376 | <ti>Default PPC 2005.0 profile for 2.6 kernels</ti> |
|
|
377 | <ti></ti> |
|
|
378 | </tr> |
|
|
379 | <tr> |
|
|
380 | <ti>default-linux/ppc64/2005.0</ti> |
|
|
381 | <ti>Default PPC64 2005.0 profile for 2.6 kernels</ti> |
|
|
382 | <ti></ti> |
|
|
383 | </tr> |
|
|
384 | <tr> |
|
|
385 | <ti>default-linux/s390/2005.0</ti> |
|
|
386 | <ti>Default S390 2005.0 profile</ti> |
|
|
387 | <ti></ti> |
|
|
388 | </tr> |
|
|
389 | <tr> |
|
|
390 | <ti>default-linux/sparc/sparc32/2005.0</ti> |
|
|
391 | <ti>Default Sparc 32-bit 2005.0 profile</ti> |
|
|
392 | <ti></ti> |
|
|
393 | </tr> |
|
|
394 | <!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm |
|
|
395 | No subprofiles for sparc |
|
|
396 | <tr> |
|
|
397 | <ti>default-linux/sparc/sparc32/2005.0/2.6</ti> |
|
|
398 | <ti>Sparc 32-bit 2005.0 profile for 2.6 kernels</ti> |
|
|
399 | <ti></ti> |
|
|
400 | </tr> |
|
|
401 | --> |
|
|
402 | <tr> |
|
|
403 | <ti>default-linux/sparc/sparc64/2005.0</ti> |
|
|
404 | <ti>Default Sparc 64-bit 2005.0 profile</ti> |
|
|
405 | <ti></ti> |
|
|
406 | </tr> |
|
|
407 | <!-- http://dev.gentoo.org/~dsd/kernel-2.6.htm |
|
|
408 | No subprofiles for sparc |
|
|
409 | <tr> |
|
|
410 | <ti>default-linux/sparc/sparc64/2005.0/2.6</ti> |
|
|
411 | <ti>Sparc 64-bit 2005.0 profile for 2.6 kernels</ti> |
|
|
412 | <ti></ti> |
|
|
413 | </tr> |
|
|
414 | --> |
|
|
415 | <tr> |
|
|
416 | <ti>default-linux/x86/2005.0</ti> |
|
|
417 | <ti>Default x86 2005.0 profile for 2.6 kernels</ti> |
|
|
418 | <ti></ti> |
|
|
419 | </tr> |
|
|
420 | <tr> |
|
|
421 | <ti>default-linux/x86/2005.0/2.4</ti> |
|
|
422 | <ti>x86 2005.0 profile for 2.4 kernels</ti> |
|
|
423 | <ti></ti> |
|
|
424 | </tr> |
|
|
425 | </table> |
|
|
426 | |
|
|
427 | <p> |
|
|
428 | To switch to the selected profile, point the <path>/etc/make.profile</path> |
|
|
429 | symlink to the new location. Make sure your Portage is updated before you change |
|
|
430 | your profile! |
|
|
431 | </p> |
|
|
432 | |
|
|
433 | <pre caption="Changing to a 2005.0 profile"> |
|
|
434 | # <i>rm /etc/make.profile</i> |
|
|
435 | # <i>ln -s ../usr/portage/profiles/</i><selected profile><i> /etc/make.profile</i> |
|
|
436 | </pre> |
|
|
437 | |
|
|
438 | <p> |
|
|
439 | If you are running a Linux 2.4-based system but want to migrate to a 2.6-based |
|
|
440 | kernel, make sure you read our <uri link="/doc/en/migration-to-2.6.xml">Gentoo |
|
|
441 | Linux 2.6 Migration Guide</uri>. |
|
|
442 | </p> |
|
|
443 | |
|
|
444 | </body> |
|
|
445 | </section> |
|
|
446 | <section> |
|
|
447 | <title>Updating to 2004.3</title> |
|
|
448 | <body> |
|
|
449 | |
|
|
450 | <p> |
|
|
451 | With the introduction of the 2004.3 profiles, users are not going to see huge |
|
|
452 | modifications of their systems (see below for details). However, Gentoo |
|
|
453 | developers decided to push out this new profile and to deprecate quite a few of |
|
|
454 | the old ones to speed up the adoption of <e>stacked profiles</e>, that is, the |
|
|
455 | profiles that follow the new layout of the <path>/usr/portage/profiles</path> |
|
|
456 | directory, for instance |
|
|
457 | <path>/usr/portage/profiles/default-linux/x86/2004.3</path> (supported by |
|
|
458 | Portage 2.0.51 or later). |
|
|
459 | </p> |
|
|
460 | |
|
|
461 | <p> |
|
|
462 | To switch to the 2004.3 profile, point the <path>/etc/make.profile</path> |
|
|
463 | symlink to the new location: |
|
|
464 | </p> |
|
|
465 | |
|
|
466 | <warn> |
|
|
467 | Don't forget to upgrade Portage <e>before</e> you change your profile!!! |
|
|
468 | </warn> |
|
|
469 | |
|
|
470 | <pre caption="Updating the /etc/make.profile symlink"> |
|
|
471 | <comment>substitute <arch> with your arch</comment> |
|
|
472 | # <i>rm /etc/make.profile</i> |
|
|
473 | # <i>ln -s ../usr/portage/profiles/default-linux/<arch>/2004.3 /etc/make.profile</i> |
|
|
474 | </pre> |
|
|
475 | |
|
|
476 | <p> |
|
|
477 | <b>All archs</b> - As said above, there are no big changes introduced in this |
|
|
478 | profile. However, it should be noted that <c>sys-apps/slocate</c> and |
|
|
479 | <c>net-misc/dhcpcd</c> are no longer considered system packages. This means |
|
|
480 | that if you run <c>emerge --depclean</c>, Portage will try to remove them from |
|
|
481 | your system. If you need any of those packages, add them to |
|
|
482 | <path>/var/lib/portage/world</path> after the profile switch, or manually |
|
|
483 | emerge them. |
|
|
484 | </p> |
|
|
485 | |
|
|
486 | <p> |
|
|
487 | <b>ppc</b> - <c>sys-fs/udev</c> is now the default instead of |
|
|
488 | <c>sys-fs/devfs</c> for newly installed machines. This has no |
|
|
489 | effect on already installed machines, though. |
|
|
490 | </p> |
|
|
491 | |
|
|
492 | </body> |
|
|
493 | </section> |
|
|
494 | <section> |
|
|
495 | <title>Updating Portage to Support Cascading Profiles</title> |
|
|
496 | <body> |
|
|
497 | |
|
|
498 | <p> |
|
|
499 | Although this section does not seem to integrate well in this upgrading guide, |
|
|
500 | it is quite important. Any profile listed above this section requires a Portage |
|
|
501 | version that supports cascading profiles. However, some obsoleted profiles don't |
|
|
502 | allow the user to upgrade Portage or the user is using a profile that isn't |
|
|
503 | available anymore - any attempt to upgrade Portage will result in a failure. |
|
|
504 | </p> |
|
|
505 | |
|
|
506 | <p> |
|
|
507 | To work around this problem, users can set a temporary symbolic link to the |
|
|
508 | <e>obsolete</e> profile, allowing them to upgrade their Portage after which |
|
|
509 | they can continue with the upgrade procedure set forth in this guide. Please |
|
|
510 | substitute <c><arch></c> with your respective architecture: |
|
|
511 | </p> |
|
|
512 | |
|
|
513 | <pre caption="Updating Portage through the obsolete profile"> |
|
|
514 | # <i>rm /etc/make.profile</i> |
|
|
515 | # <i>cd /etc</i> |
|
|
516 | # <i>ln -sf ../usr/portage/profiles/obsolete/<arch> make.profile</i> |
|
|
517 | # <i>emerge -n '>=sys-apps/portage-2.0.51'</i> |
|
|
518 | </pre> |
|
|
519 | |
|
|
520 | </body> |
|
|
521 | </section> |
|
|
522 | <section> |
| 254 | <title>Updating to 2004.2</title> |
523 | <title>Updating to 2004.2</title> |
| 255 | <body> |
524 | <body> |
| 256 | |
525 | |
| 257 | <p> |
526 | <p> |
| 258 | To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> symlink |
527 | To switch to the 2004.2 profile, point the <path>/etc/make.profile</path> |
| 259 | to the new location: |
528 | symlink to the new location: |
| 260 | </p> |
529 | </p> |
|
|
530 | |
|
|
531 | <warn> |
|
|
532 | Don't forget to upgrade Portage <e>before</e> you change your profile!!! |
|
|
533 | </warn> |
| 261 | |
534 | |
| 262 | <pre caption="Updating the /etc/make.profile symlink"> |
535 | <pre caption="Updating the /etc/make.profile symlink"> |
| 263 | <comment>substitute <arch> with your arch</comment> |
536 | <comment>substitute <arch> with your arch</comment> |
| 264 | # <i>rm /etc/make.profile</i> |
537 | # <i>rm /etc/make.profile</i> |
| 265 | # <i>ln -s ../usr/portage/profiles/default-linux/<arch>/2004.2 /etc/make.profile</i> |
538 | # <i>ln -s ../usr/portage/profiles/default-linux/<arch>/2004.2 /etc/make.profile</i> |
| … | |
… | |
| 284 | <section> |
557 | <section> |
| 285 | <title>Updating to 2004.0</title> |
558 | <title>Updating to 2004.0</title> |
| 286 | <body> |
559 | <body> |
| 287 | |
560 | |
| 288 | <p> |
561 | <p> |
| 289 | To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> symlink |
562 | To switch to the 2004.0 profile, point the <path>/etc/make.profile</path> |
| 290 | to the new location: |
563 | symlink to the new location: |
| 291 | </p> |
564 | </p> |
| 292 | |
565 | |
| 293 | <pre caption="Updating the /etc/make.profile symlink"> |
566 | <pre caption="Updating the /etc/make.profile symlink"> |
| 294 | <comment>substitute <arch> with your arch</comment> |
567 | <comment>substitute <arch> with your arch</comment> |
| 295 | # <i>rm /etc/make.profile</i> |
568 | # <i>rm /etc/make.profile</i> |
Parent Directory
| 
Revision Log
| 
Patch