Code: Select all
emerge --info
Portage 2.1.1-r1 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.4-r3, 2.6.16.18 i586)
What kind of unholy magic did you do to make gcc-4.1 upgrade smoothly?nevynxxx wrote:For a(n apparently) different perspective
I have never (ever) run emerge -e system or emerge -e world.Code: Select all
emerge --info Portage 2.1.1-r1 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.4-r3, 2.6.16.18 i586)
This system has been installed and working for 2 years at least......pitty I can't remember the command that tells you when the system was installed.
If I remember rightly I followed a migration guide on the wiki.rokstar83 wrote:
What kind of unholy magic did you do to make gcc-4.1 upgrade smoothly?
Its not really an obsession when you are upgrading GCC, its more out of necessity. When the ABI changes you run the risk of libs and progs not playing nicely with one another. I guess if you upgrade the dependancies with the program in theory you should be okay, but i'm willing to be that something silly could happen really easily so i'd rather not take the chance. I usually only use empty-tree to emulate stage 1 installations on a new box, or for these massive ABI-breaking gcc upgrades. Doing it any other time just seems like i'm needlessly heating my home with the CPU.nevynxxx wrote:If I remember rightly I followed a migration guide on the wiki.rokstar83 wrote:
What kind of unholy magic did you do to make gcc-4.1 upgrade smoothly?
i seem to remember I had more problems with glibc, requiring a fix from the forums.
I emerge -uDav world on a weekly basis give or take, so everything will be updated eventually.
Oh, this is on my router, and the postfix/LAMP/cacti server at work that servers the intranet and filters all the firms mail. With no downtime.
I don't get the current obsession with the -e flag.
Unless you're watching your machine 24/7, you don't see 'em.Gergan Penkov wrote:Well how hard is to implement the notices for broken packages
Have a look at portlog..Corona688 wrote:Unless you're watching your machine 24/7, you don't see 'em.Gergan Penkov wrote:Well how hard is to implement the notices for broken packages
That's one thing that could be changed, I think. Those should be logged.
Look at Genone's reply to this thread. It's an elegant, simple way of logging the messages. After each emerge I just examine the log file it creates and act on the information. It's brilliant.Corona688 wrote:Unless you're watching your machine 24/7, you don't see 'em.Gergan Penkov wrote:Well how hard is to implement the notices for broken packages
That's one thing that could be changed, I think. Those should be logged.
Code: Select all
# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
CFLAGS="-march=athlon64 -O3 -pipe -msse -mmmx -m3dnow -msse2 -msse3 -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j3"
ACCEPT_KEYWORDS="~amd64"
LDFLAGS="-Wl,--hash-style=both"
GENTOO_MIRRORS="http://gentoo.osuosl.org/ ftp://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/$
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
PORTDIR_OVERLAY="/usr/local/portage"
PORTDIR_OVERLAY="${PORTDIR_OVERLAY} /usr/local/overlays/toolchain_overlay"
USE="tiff X usb pdf aac aim alsa aoss cdparanoia cdr directfb divx dvd dvdr dvdread emacs
emacs-w3 firefox foomaticdb gcj gif gnome gtk gtk2 gtkhtml hal ieee1394
java javascript jpeg jpeg2k kdeenablefinal mime mp3 mpeg mpeg2 mplayer
no-seamonkey nsplugin nvidia png ogg opengl oss quicktime theora vorbis matroska win32codecs dbus hashstyle cairo xpm"
VIDEO_CARDS="nv vesa"
ALSA_CARDS="intel8x0"
source /usr/portage/local/layman/make.conf
Well yeah. That's the other thing. If you do emerge -uDav world, then almost everything gets filtered through eventually.nevynxxx wrote:If I remember rightly I followed a migration guide on the wiki.rokstar83 wrote:
What kind of unholy magic did you do to make gcc-4.1 upgrade smoothly?
i seem to remember I had more problems with glibc, requiring a fix from the forums.
I emerge -uDav world on a weekly basis give or take, so everything will be updated eventually.
Oh, this is on my router, and the postfix/LAMP/cacti server at work that servers the intranet and filters all the firms mail. With no downtime.
I don't get the current obsession with the -e flag.
How so? What is it about a LAMP server that means it doesn't need an emerge -e world, when a desktop system does?devsk wrote:that's the key to your success! What you claimed doesn't apply in general.nevynxxx wrote:Oh, this is on my router, and the postfix/LAMP/cacti server at work that servers the intranet and filters all the firms mail. With no downtime.
Code: Select all
#!/bin/bash
SYSTEM=`emerge -ep system | cut -c 17- |sed s/^/=/g | sed s/'USE.*$"'/' '/ | sed -e '1,4d' | sed s/' .*$'/' '/`
WORLD_COMPLETE=`emerge -ep world | cut -c 17- |sed s/^/=/g | sed s/'USE.*$"'/' '/ | sed -e '1,4d' | sed s/' .*$'/' '/`
WORLD_MINUS_SYSTEM=`for package in $WORLD_COMPLETE; do
if !(echo "$SYSTEM" | grep -q "$package")
then
echo "$package"
fi
done`
emerge $SYSTEM
emerge $WORLD_MINUS_SYSTEMaidanjt wrote:You see, instead of arguing from ignorance, and fear, there is only one way to verify a theory. And that's not by clutching a black book and begging the sky fairy for deliverance from the mad scientists and their big machines.
Yeah, but on my system the 'system' file includes some things that take _FOREVER_ to build (like glibc and gcc). So that little script is saving me a fair amount of time on this update.rokstar83 wrote:There is another thread out there that I can't seem to find about someone exposing the myth of the double system and world emerge. There was also instructions on what you actually need to rebuild in system that is crucial to rebuilding world instead of the whole thing, which is mostly just the toolchain.
Personally i've found that the system emerge is so much shorter than world that i'm willing to patient and let system get done twice. It doesn't hurt any one an typically i'm going to let it run throughout the night anyways.
aidanjt wrote:You see, instead of arguing from ignorance, and fear, there is only one way to verify a theory. And that's not by clutching a black book and begging the sky fairy for deliverance from the mad scientists and their big machines.
For me its only gcc and glibc that slow it down, but those are nothing compared to say gtk, qt, mythtv, openoffice, split xorg, etc. I've guess i've also been fortunate as of late as my newer computers are all less than a year old and as such they burn through these emerges so fast its now the harddrive thats really slowing things down.UberPinguin wrote:Yeah, but on my system the 'system' file includes some things that take _FOREVER_ to build (like glibc and gcc). So that little script is saving me a fair amount of time on this update.rokstar83 wrote:There is another thread out there that I can't seem to find about someone exposing the myth of the double system and world emerge. There was also instructions on what you actually need to rebuild in system that is crucial to rebuilding world instead of the whole thing, which is mostly just the toolchain.
Personally i've found that the system emerge is so much shorter than world that i'm willing to patient and let system get done twice. It doesn't hurt any one an typically i'm going to let it run throughout the night anyways.
Agreed. OpenOffice is usually a 1-2 day build on my laptop - running constantly. My p4 is starting to show its age, too.rokstar83 wrote: For me its only gcc and glibc that slow it down, but those are nothing compared to say gtk, qt, mythtv, openoffice, split xorg, etc. I've guess i've also been fortunate as of late as my newer computers are all less than a year old and as such they burn through these emerges so fast its now the harddrive thats really slowing things down.
aidanjt wrote:You see, instead of arguing from ignorance, and fear, there is only one way to verify a theory. And that's not by clutching a black book and begging the sky fairy for deliverance from the mad scientists and their big machines.
aidanjt wrote:You see, instead of arguing from ignorance, and fear, there is only one way to verify a theory. And that's not by clutching a black book and begging the sky fairy for deliverance from the mad scientists and their big machines.
Weirdness. I must have emerged the whole of OpenOffice at some point because when I had to re-build my laptop, it went straight for the source not binary ebuild.UberPinguin wrote:If you emerge app-office/openoffice-bin instead of plain openoffice, then your updates should continue to pull the -bin version. As far as I can tell, there's no USE flag for binary builds that would affect openoffice.
That's the one I did have, and it would crash on boot maybe 60-80% of the time. That and any documents that had been shared with MSOffice would crash the works - assuming I go the thing running. I also have a hard time with Gimpshop (A GIMP variant). Both require the X11 mock-up, so chances are the root of the problem is there.UberPinguin wrote:Try http://porting.openoffice.org/mac/download/IntelDownload.html for openoffice onyour iMac.
Actually, I'm thinking I'll go with Paralells. For $80 I can run whatever OS like Wine and make use of whatever Weener-doze software I need.UberPinguin wrote: Also, you can set up a VNC server and use Chicken of the VNC on your iMac so that you can still use that big keyboard and screen :)
Man if gentoo had a open request for developers to work on bin and or src version that was supported and stable for 6 months the problem of maintaining that would be totaly ofset by the hords of developers flooding back to Gentoo. Plus having a easy to use version of gentoo would attract lots of fresh liinux converts and give them a way to ease in.Genone wrote:No. I said that you want to use a similar release system like those used in binary distros, however that doesn't exist in Gentoo (yet).ValenceParadigm wrote:So let me get this straight: What you're suggesting here is that people like me who are too busy doing other things than updating their gentoo box every 4 weeks should dump gentoo for a binary distro and STFU?Genone wrote: ...People either wouldn't see a notice about the new version or just ignore it and stay on their current version forever (until it gets removed from the tree and everybody starts crying)....
...versioned/frozen tree that doesn't receive any major updates, and when you're prepared for a big update you get a new tree version and rebuild everything. Basically the same process as with most binary distros.
Dunno if you've understood the kind of work required there: You'll need a group of people that permanently monitor the regular tree for changes (not just version updates), decide if a change is important and eventually backport that change to a tree snapshot in a least-intrusive way, that means to avoid any functional changes, so if package foo has a critical security bug and we fix it in the main tree by bumping foo to a new major version (with new config file layout and different soname for example) you can't really do the same in that "frozen" tree. It's a rather boring job and needs a lot of time, so I doubt that there are a lot of (qualified) people who would like to do that regularly. And even if you start with only the core system (e.g. USE=-* emerge -ep system) for one or two archs I'd say you need already 3-5 people, for the whole tree it's more in the range of a hundred or so (considering that it would be basically a fork of the main tree).turtles wrote:Man if gentoo had a open request for developers to work on bin and or src version that was supported and stable for 6 months the problem of maintaining that would be totaly ofset by the hords of developers flooding back to Gentoo. Plus having a easy to use version of gentoo would attract lots of fresh liinux converts and give them a way to ease in.Genone wrote: No. I said that you want to use a similar release system like those used in binary distros, however that doesn't exist in Gentoo (yet).
. I like that. I will start a thread when I get ready to reinstall ( my desktop is soo hosed by the gcc upgrade) I will install alot of partitons and keep a common /boot /home /swap for l 4 different OS's (gentoo stable, gentoo test out different upgrades first, freeBSD, and ubuntu).Do some planning. I'm currently rebuilding my system in a chroot at my convenience. When its done, I'll just repoint to the new / and update my fstab.
That's essentially what the script I posted above does, if anyone would like an example of functioning code for that.SirYes wrote:BTW. emerge -e world may also be shortened by redirecting the output of emerge -pe world to a file (for example, with leaving only the names and versions of packages through some cut/sed/awk magic) and removing packages which you know would be unnecessary. Then another emerge -av `cat file` should do the trick. Not the easiest way, but workable.
aidanjt wrote:You see, instead of arguing from ignorance, and fear, there is only one way to verify a theory. And that's not by clutching a black book and begging the sky fairy for deliverance from the mad scientists and their big machines.
