swift       05/09/20 18:24:14

  Modified:    xml/htdocs/doc/en gentoo-upgrading.xml
  Log:
  #102918 - Update on upgrading guide to reflect use of obsolete profile for 
portage upgrade

Revision  Changes    Path
1.25      +28 -1     xml/htdocs/doc/en/gentoo-upgrading.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-upgrading.xml?rev=1.25&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-upgrading.xml?rev=1.25&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/gentoo-upgrading.xml.diff?r1=1.24&r2=1.25&cvsroot=gentoo

Index: gentoo-upgrading.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- gentoo-upgrading.xml        12 Aug 2005 10:29:12 -0000      1.24
+++ gentoo-upgrading.xml        20 Sep 2005 18:24:14 -0000      1.25
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 
1.24 2005/08/12 10:29:12 neysx Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/gentoo-upgrading.xml,v 
1.25 2005/09/20 18:24:14 swift Exp $ -->
 
 <guide link="/doc/en/gentoo-upgrading.xml">
 <title>Gentoo Upgrading Guide</title>
@@ -499,6 +499,33 @@
 </body>
 </section>
 <section>
+<title>Updating Portage to Support Cascading Profiles</title>
+<body>
+
+<p>
+Although this section does not seem to integrate well in this upgrading guide,
+it is quite important. Any profile listed above this section requires a Portage
+version that supports cascading profiles. However, some obsoleted profiles 
don't
+allow the user to upgrade Portage or the user is using a profile that isn't
+available anymore - any attempt to upgrade Portage will result in a failure.
+</p>
+
+<p>
+To work around this problem, users can set a temporary symbolic link to the
+<e>obsolete</e> profile, allowing them to upgrade their Portage after which
+they can continue with the upgrade procedure set forth in this guide:
+</p>
+
+<pre caption="Updating Portage through the obsolete profile">
+# <i>rm /etc/make.profile</i>
+# <i>cd /etc</i>
+# <i>ln -sf ../usr/portage/profiles/obsolete make.profile</i>
+# <i>emerge -n '>=sys-apps/portage-2.0.51'</i>
+</pre>
+
+</body>
+</section>
+<section>
 <title>Updating to 2004.2</title>
 <body>
 



-- 
[email protected] mailing list

Reply via email to