Linked by Eugenia Loli on Thu 31st Aug 2006 01:09 UTC, submitted by Jeff
Gentoo is reporting on the release of Gentoo Linux 2006.1. Building on the strengths of previous releases and featuring all of Gentoo's well-documented flexibility, performance and portability, this release is now available on all supported architectures. The most popular architectures now use GCC 4.1, glibc 2.4 and baselayout 1.12.1, as well as including a new profile layout, with seperate desktop and server profiles.
Thread beginning with comment 157310
To read all comments associated with this story, please click here.
Oba oba
by gothicknight on Thu 31st Aug 2006 01:23 UTC
Member since:

Finaly }:>

Reply Score: 1

RE: Oba oba
by siimo on Thu 31st Aug 2006 07:33 in reply to "Oba oba"
siimo Member since:

Isn't it a rolling release anyway?

Could have just grabbed 2006.0 and emerge vauD world ;)
Unless you have really new hardware that wasn't detected by 2006.0 CD

Reply Parent Score: 2

RE[2]: Oba oba
by kerframil on Thu 31st Aug 2006 11:36 in reply to "RE: Oba oba"
kerframil Member since:

Upgrades aren't necessarily that simple, even in Gentoo. Firstly, one ought to update the /etc/make.profile symlink to point to the appropriate portage profile. Secondly, consider the gcc upgrading guide:

It specifically states that there have been some incompatible ABI changes between binaries produced by gcc-3.4 and gcc-4.1 - presumably the C++ runtime library again. In any case, this is an important issue if the user decideds to explicitly activate the new instance of gcc with the gcc-config tool after installing gcc-4.1. As the majority of upgraders will most probably want to do exactly that, the most sensible procedure would be to to carry out the instructions mentioned in the guide: upgrade gcc, switch/activate, emerge libtool, emerge -e world then optionally remove the older version of the compiler. If you think about it, running emerge -uDN world would be a complete waste of time unless one intended to stay with gcc-3.x for the forseeable future ...

Finally, depending on the exact circumstances and not necessarily relating to the variations between official release snapshots, upgrades of certain packages can sometimes entail particular steps to "clean up" afterwards. This might entail running perl-cleaner, python-updater and/or revdep-rebuild (I'm sure I don't need to mention dispatch-conf/etc-update).

Anyway, this looks like a good release - well done to the Gentoo release engineering team ;)

Reply Parent Score: 3

RE[2]: Oba oba
by kerframil on Thu 31st Aug 2006 11:42 in reply to "RE: Oba oba"
kerframil Member since:

Also, I forgot to add that when switching gcc versions one really ought to rebuild the kernel and kernel modules in their entirety. The kernel does not like having portions of itself built with different compilers. I've seen this happen quite often with people who build external modules (such as nvidia-drivers), expecting to be able to use the modules with a kernel that was originally compiled with an older gcc version. It doesn't work. Although it's easily dealt with, the point is that there is no "automagic" way of taking care of all of this.

Edited 2006-08-31 11:42

Reply Parent Score: 2