Posted by
timothy
on from the sane-versioning-system-is-a-plus dept.
Dreadlord writes "Gentoo has released 2004.3 for x86, amd64, hppa, ppc, sparc, and an initial release for ppc64. You can read the information page, the changelog, or go straight to the mirrors, or better yet, the torrents."
Just stressing..
by
iswm
·
· Score: 4, Informative
That this is just a new version of the LiveCD. No need to reinstall the core system.
-- Buckethead
Re:Obligatory Gentoo Joke
by
BlindSpy
·
· Score: 5, Informative
these are only the versions of the live CD. Your actual Gentoo install has no version number because its always the latest. So regardless if you used 2004.0 or 2004.3 to install - you ultimately have the same version after you've completely installed.
-- Whoever dies with the most toys wins.
Someone's got to say it
by
Stevyn
·
· Score: 5, Informative
Before all the dumb jokes start, here's what this means:
If you want to install Gentoo for the first time, you can download a bunch of precompiled packages and complete an installation in a few hours or so, probably less.
If you already have Gentoo on your system, this won't mean much since you can update the everything by with the command(s) "#emerge sync; emerge -uDp world"
This does not mean everyone with Gentoo is going to be compiling for days. You're still stuck with us for a while.
Re:Someone's got to say it
by
solarium_rider
·
· Score: 5, Informative
actually, no need to do both commands anymore.
With the latest version of portage, you can just run
# emerge -uDa world
The -a is short for --ask. That will ask you if you really want to emerge the listed packages.
For those who think `emerge sync && emerge -uD world` will update your system:
Don't forget to update the/etc/make.profile link after an `emerge sync`. The sync will place the new profile in/usr/portage/profiles. From the Gentoo Upgrading Guide:
substitute $arch with your arch # rm/etc/make.profile # ln -s../usr/portage/profiles/default-linux/$arch/2004.3/etc/make.profile
--
http://www.masturbateforpeace.com/
Compile...?
by
tanveer1979
·
· Score: 4, Informative
Umm, Compiling everything is this big misconception. There are prebuilt binary packages available for most common applications for most architechtures. Infact if gentoo binary package is not there, there is a fair chance you will not get the binary package for other distros as well. I am using gentoo on my AMD64, and i do not want to go back to any other distro.
But then its always a matter of choice. And if the only reason of you not using gentoo is compiling everything from source, then its the wrong reason.
-- My Aurora : http://www.youtube.com/watch?v=o91ZsGwJYyg
FB : https://www.facebook.com/TanveersPhotography
Re:I HATE YOU TOO GENTOO
by
qtothemax
·
· Score: 4, Informative
The big question... does it actually work and take care of everything?
Yes. The only other thing you might want to do (though its usually not necessary) is to update the profile. After an emerge -u world, everything will be current. With gentoo version numbers mean next to nothing. New versions are usually just updates to the installer livecd itself to fix bugs and support more hardware. The packages are updated constantly, not just when new gentoo releases come out.
Re:version dependencies
by
NotoriousQ
·
· Score: 5, Informative
To add to this, there are two modes of masking:
the hard mask -- which means that the package maintainer does not deem the package to be safe at all.
the ~ mask -- which is the unstable package. You can tell the emerge system that you wish to have the unstable system, in which case it will ignore the ~ mask.
Also, there is such a thing as profiles. They have things such as the version of gcc and glibc that your system uses. If you chose the right profile, you can continue building the system with gcc 2.95. Although the packages are not well tested with it, and no one wants to specifically check and mask each package with older profiles.
I'm sure you know it's source based by the dozens of +5 Funny's..
What's good? The package system is transparent and extremely hackable. If you don't touch it, it works just like apt or yum. But if you want to make a change, its extremely easy to pop the ebuild in vim and change it, or fork your own version. Also very easy to produce a "package" for any specific version you like, often as simple as renaming a file.
What's bad? Initial installation takes a while (I can get a useable box in ~ 3 hours. Gnome & co take the longest). Not recommended for slow computers (anything made in the last four years ought to be fine) due to frequent code compilation. Portage moves very very fast. Lots of new versions released every week.
I run it everywhere, including this here Toshiba Tecra S-1 notebook.
First off, I had submitted Slashdot an official press release which was much more verbose and gave a nice list of reasons for the release and things changed since the last release, but since the editors are a bunch of tools and don't pay attention to what they're adding to the site, it all got lost.
Anyway, for the x86 platform, the primary reason for the getting a newer release is improved hardware support. The newer LiveCD for x86 supports the new Dell EM64T machines and also has vastly improved SATA support over previous releases. This is also the first release where all of the arch teams worked very closely together throughout the entire release process. This is also our first official PPC64 release. The submitter of this story also completely missed the fact that we have a new Alpha release under/experimental, and you can also find embedded stages for arm, mips, ppc, and x86 under/experimental.
Slashdot Mirror
That this is just a new version of the LiveCD. No need to reinstall the core system.
Buckethead
these are only the versions of the live CD. Your actual Gentoo install has no version number because its always the latest. So regardless if you used 2004.0 or 2004.3 to install - you ultimately have the same version after you've completely installed.
Whoever dies with the most toys wins.
Before all the dumb jokes start, here's what this means:
If you want to install Gentoo for the first time, you can download a bunch of precompiled packages and complete an installation in a few hours or so, probably less.
If you already have Gentoo on your system, this won't mean much since you can update the everything by with the command(s) "#emerge sync; emerge -uDp world"
This does not mean everyone with Gentoo is going to be compiling for days. You're still stuck with us for a while.
emerge sync && emerge -uD world
There was Cowboy Neal at the wheel of a bus to never-ever land.
For those who think `emerge sync && emerge -uD world` will update your system:
/etc/make.profile link after an `emerge sync`. The sync will place the new profile in /usr/portage/profiles. From the Gentoo Upgrading Guide:
/etc/make.profile ../usr/portage/profiles/default-linux/$arch/2004.3 /etc/make.profile
Don't forget to update the
substitute $arch with your arch
# rm
# ln -s
http://www.masturbateforpeace.com/
But then its always a matter of choice. And if the only reason of you not using gentoo is compiling everything from source, then its the wrong reason.
My Aurora : http://www.youtube.com/watch?v=o91ZsGwJYyg
FB : https://www.facebook.com/TanveersPhotography
The big question... does it actually work and take care of everything?
Yes. The only other thing you might want to do (though its usually not necessary) is to update the profile. After an emerge -u world, everything will be current. With gentoo version numbers mean next to nothing. New versions are usually just updates to the installer livecd itself to fix bugs and support more hardware. The packages are updated constantly, not just when new gentoo releases come out.
To add to this, there are two modes of masking:
the hard mask -- which means that the package maintainer does not deem the package to be safe at all.
the ~ mask -- which is the unstable package. You can tell the emerge system that you wish to have the unstable system, in which case it will ignore the ~ mask.
Also, there is such a thing as profiles. They have things such as the version of gcc and glibc that your system uses. If you chose the right profile, you can continue building the system with gcc 2.95. Although the packages are not well tested with it, and no one wants to specifically check and mask each package with older profiles.
badness 10000
I'm sure you know it's source based by the dozens of +5 Funny's..
What's good? The package system is transparent and extremely hackable. If you don't touch it, it works just like apt or yum. But if you want to make a change, its extremely easy to pop the ebuild in vim and change it, or fork your own version. Also very easy to produce a "package" for any specific version you like, often as simple as renaming a file.
What's bad? Initial installation takes a while (I can get a useable box in ~ 3 hours. Gnome & co take the longest). Not recommended for slow computers (anything made in the last four years ought to be fine) due to frequent code compilation. Portage moves very very fast. Lots of new versions released every week.
I run it everywhere, including this here Toshiba Tecra S-1 notebook.
No, I did not read the f***ing article!
BTW, this is probably why you should do it per hand
First off, I had submitted Slashdot an official press release which was much more verbose and gave a nice list of reasons for the release and things changed since the last release, but since the editors are a bunch of tools and don't pay attention to what they're adding to the site, it all got lost.
Anyway, for the x86 platform, the primary reason for the getting a newer release is improved hardware support. The newer LiveCD for x86 supports the new Dell EM64T machines and also has vastly improved SATA support over previous releases. This is also the first release where all of the arch teams worked very closely together throughout the entire release process. This is also our first official PPC64 release. The submitter of this story also completely missed the fact that we have a new Alpha release under /experimental, and you can also find embedded stages for arm, mips, ppc, and x86 under /experimental.