Gentoo 1.4 Upgrade Guide Renée Michù Gastòn Ledoÿeñ A method for upgrading older Gentoo installations in place to Gentoo 1.4 v0.3 October 2, 2004 Before you begin
Ignore content

As mentioned later on, you should not bother about the content of this document. Its sole purpose is to let you show that you can fix a totally broken GuideXML file and apply coding style. If you think it's taking too much of your time then you really need the practice.

General notes

Whenever the code listings suggest running the emerge command, it is always a good idea to make a test run of the command using the -p or --pretend option to make sure that the command will do what you expect it to do.

 Upgrading in place
Get Portage as current as possible

Some of the syntax of current ebuilds is unreadable by older versions of Portage. If you don't have at least Portage 2.0.44, try upgrading Portage. 

	# emerge --sync
	# emerge -u portage
If your Portage version is very old, you may get an error message containing the phrase "unscriptable object". Read and follow the instructions in /usr/portage/sys-apps/portage/files/README.RESCUE. Your Portage install should then be current.

You will find more information about Portage in our Handbook.
Preparing GCC for cohabitation

You will be installing a newer version of GCC during this upgrade. Versions of GCC older than 2.95.3-r8 are not designed to have multiple versions of GCC installed. You must therefore upgrade GCC to at least version 2.95.3-r8. This will also have the beneficial side-effect of installing the gcc-config package on your system, which can be used to switch back and forth between various installed versions of GCC.

# emerge -u gcc

You can now check to see if gcc-config is working properly:

# gcc-config --get-current-profile

This should return i686-pc-linux-gnu-2.95.3 on most x86 systems. Older systems may return i586-pc-linux-gnu-2.95.3.

Installing GCC 3

Edit /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild and search for the line containing DEPEND. Remove the glibc dependency and save the ebuild. 

# vim /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild

install the latest GCC version on your system:
# USE="-java" emerge /usr/portage/sys-devel/gcc/gcc-3.2.2.ebuild
Changing profiles

Now you need to change two sets of profiles: your gcc-config profile and your Portage profile.

# cd /etc
# rm make.profile
# ln -s ../usr/portage/profiles/default-x86-1.4 make.profile (Replace "x86" with your architecture)

# gcc-config --list-profiles (Note the one for the version you just emerged, use it below)
# gcc-config i686-pc-linux-gnu-3.2.2 (Replace with the version you noted above)
This has nothing to do with the above

During the meeting:

  • Keep the meeting flowing. This means maintaining focus on the agenda and the objectives of the meeting.
  • Keep the meeting within its allotted time frame (usually one hour)
  • Allow the presentation of an agenda item by the person responsible for that item, before any questions and discussion is undertaken.
  • Get responses from all members before moving onto the next agenda item.
  • Briefly summarize unresolved business. This may include the result of the discussion, specific actions that are to be taken, who's responsible for working on what etc.
  • Allow all attendees to be able to discuss their concerns after the agenda items have been discussed.