Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 65744 Details for
Bug 102212
Update gentoo-upgrading.xml for 2005.1
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
gentoo-upgrading-2005.1.patch
gentoo-upgrading-2005.1.patch (text/plain), 3.32 KB, created by
Gregorio Guidi (RETIRED)
on 2005-08-12 03:18:44 UTC
(
hide
)
Description:
gentoo-upgrading-2005.1.patch
Filename:
MIME Type:
Creator:
Gregorio Guidi (RETIRED)
Created:
2005-08-12 03:18:44 UTC
Size:
3.32 KB
patch
obsolete
>--- gentoo-upgrading.xml.orig 2005-08-12 12:09:58.000000000 +0200 >+++ gentoo-upgrading.xml 2005-08-12 12:10:06.000000000 +0200 >@@ -99,8 +99,8 @@ > The profile in use is determined by the symbolic link > <path>/etc/make.profile</path>, which points to a subdirectory of > <path>/usr/portage/profiles</path> which holds the profile files. For >-instance, the default x86 2005.0 profile can be found >-at <path>/usr/portage/profiles/default-linux/x86/2005.0</path>. >+instance, the default x86 2005.1 profile can be found >+at <path>/usr/portage/profiles/default-linux/x86/2005.1</path>. > The files in the parent directories are part of the profile as well (and > are therefore shared by different subprofiles). This is why we call these > <e>cascaded profiles</e>. >@@ -120,8 +120,7 @@ > new versions of core packages (such as <c>baselayout</c>, <c>gcc</c>, or > <c>glibc</c>) that are incompatible with previous versions, a change in > the default USE flags or in the virtual mappings, or maybe a change in >-system-wide settings (such as defining udev to be the default manager >-for <path>/dev</path> instead of devfs). >+system-wide settings. > </p> > > </body> >@@ -153,8 +152,8 @@ > <body> > > <p> >-If a release (such as 2005.0) introduces a new profile, you have the choice >-to migrate to the new profile. >+If a release (such as 2005.1 for x86) introduces a new profile, you have the >+choice to migrate to the new profile. > </p> > > <p> >@@ -205,17 +204,17 @@ > <tr> > <th>alpha</th> > <ti>2005.0, 2005.0/2.4</ti> >- <ti>2004.3</ti> >+ <ti></ti> > </tr> > <tr> > <th>arm</th> >- <ti>2005.0</ti> > <ti>2004.3</ti> >+ <ti></ti> > </tr> > <tr> > <th>amd64</th> >- <ti>2005.0, 2005.0/no-multilib</ti> >- <ti>2004.3</ti> >+ <ti>2005.1, 2005.1/no-multilib</ti> >+ <ti>2005.0, 2005.0/no-multilib, 2004.3</ti> > </tr> > <tr> > <th>hppa</th> >@@ -225,12 +224,12 @@ > <tr> > <th>ia64</th> > <ti>2005.0</ti> >- <ti></ti> >+ <ti>2004.3</ti> > </tr> > <tr> > <th>ppc</th> >- <ti>2005.0</ti> >- <ti>2004.3, 2004.0</ti> >+ <ti>2005.1</ti> >+ <ti>2005.0, 2004.3, 2004.0</ti> > </tr> > <tr> > <th>mips</th> >@@ -239,18 +238,18 @@ > </tr> > <tr> > <th>s390</th> >- <ti>2005.0</ti> > <ti>2004.3</ti> >+ <ti></ti> > </tr> > <tr> > <th>sparc</th> >+ <ti>2005.1</ti> > <ti>2005.0</ti> >- <ti>2004.3, 2004.0</ti> > </tr> > <tr> > <th>x86</th> >+ <ti>2005.1, 2005.1/2.4</ti> > <ti>2005.0, 2005.0/2.4</ti> >- <ti>2004.3, 2004.2, 2004.0</ti> > </tr> > </table> > >@@ -261,6 +260,35 @@ > <chapter id="instructions"> > <title>Profile updating instructions</title> > <section> >+<title>Updating to 2005.1</title> >+<body> >+ >+<p> >+To switch to the 2005.1 profile, point the <path>/etc/make.profile</path> >+symlink to the new location. Make sure your Portage is updated before you change >+your profile! >+</p> >+ >+<pre caption="Changing to a 2005.1 profile"> >+# <i>rm /etc/make.profile</i> >+# <i>ln -s ../usr/portage/profiles/</i><selected profile><i> /etc/make.profile</i> >+</pre> >+ >+<p> >+<b>All archs</b> - There are no fundamental changes in this profile. No >+specific action needs to be performed. >+</p> >+ >+<p> >+<b>ppc</b> - With the 2005.1 release, the ppc and ppc64 profiles were merged >+and a number of subprofiles for specific subarchitectures were created. Make >+sure you choose the correct subprofile for your system when migrating to a >+2005.1 profile. >+</p> >+ >+</body> >+</section> >+<section> > <title>Updating to 2005.0</title> > <body> >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 102212
: 65744