23 Comments
- burke, on 10/12/2007, -3/+12Hooray Beer!
- nkassi, on 10/12/2007, -0/+8So working for the empire wasn't that great ? ;-)
- tobsterius, on 10/12/2007, -1/+9From the bug description:
I am mentoring Daniel to become a Gentoo developer again, he will come onboard
to work on grub and vmware-workstation-tools for now, later? We'll take over
the world.. er, I mean.. yeah! :)
Name: Daniel Robbins
Nick: drobbins
E-mail: drobbins.daniel@gmail.com
I believe Daniel did a good job of creating Gentoo in the first place, and
would make a excellent addition to the current developer team. - isolationism, on 10/12/2007, -0/+8Quality Control, for the most part. All you have to do is run an update (e.g. emerge world) to totally bust your system, forcing you to spend hours trawling the forums (and hours of recompiling big packages like glibc, more often than not) trying to get things fixed.
By contrast, when Ubuntu pulls an oops and breaks their package updates, it's a big deal: They fess up to it and get a fix out pronto. With Gentoo, if you get screwed by breaking poorly QA'ed toolchain libraries, the ONLY way it gets fixed is by manual intervention -- they can't just release another update to fix toolchains that are already broken.
I've been a Gentoo user for about 3 years now and love it, make no mistake about it -- I run it on two servers here and find it's "just right" for ease-of-use vs. customisability and control. But it's still a pain in the ass -- which is why I switched my Gentoo desktop to Ubuntu. It's definitely not as fast as it was, but then what's a second here and there compared to a half-day of downtime trying to get something working again after a library update gone wrong. - isolationism, on 10/12/2007, -2/+9Welcome back to Gentoo, Daniel. Here's hoping you can tighten the reins a bit and give them some more inventive direction to help solve some of the problems they've been encountering of late.
- hyperfusion, on 10/12/2007, -0/+6Gentoo uses the bug tracking system for *everything*, not just bugs.
- jimmiejaz, on 10/12/2007, -1/+6I find it rather comical this is on the bug tracker page...
- ePlus, on 10/12/2007, -0/+3YAY!
- JimXugle, on 10/12/2007, -6/+9Boo Microsft! Hooray Linux!
- nofxjunkee, on 10/12/2007, -0/+2He's not lead dev or anything. He's maintaining some packages, for now. He probably still makes money at MS, and is just getting settled now and has some time to work on Gentoo. It's not like he stopped using it overnight because he got a new job.
- fuselage, on 10/12/2007, -1/+3which problems are those?
- diecastbeatdown, on 10/12/2007, -0/+2gentoo rocks. love it, been using it for many years now.
welcome back Danny! - CharlesDarwin, on 10/12/2007, -0/+1Don't forget about how Gentoo handles Java. That ***** is not baller. =D
- serend, on 10/12/2007, -0/+1its an announcement they were announcing that he was taking part as a Dev, this isn't a bug report. look under the product category
- psylence, on 10/12/2007, -0/+1serend: Thanks for clearing that up, we were all pretty confused...
- guigouz, on 10/12/2007, -0/+1Gentoo started to get worse and worse after he left. Not a problem with emerge or manual intervention (it was always meant to work this way), I just wished the "stable" portage tree was really stable. There are many bugs that are fixed on bugzilla but don't get to the main tree, packages that have wrong md5 digest information, not to mention that the new java-config-2 is a HUGE step backwards.
Already dumped gentoo on the desktop in favor of ubuntu, probably heading to rpath linux on the servers, still got a couple of servers running it though. - pdiddle, on 10/12/2007, -0/+1"Quality Control, for the most part. All you have to do is run an update (e.g. emerge world) to totally bust your system, forcing you to spend hours trawling the forums (and hours of recompiling big packages like glibc, more often than not) trying to get things fixed."
That's total nonsense, I update my system every week and it has only failed to compile a package or left me with a problem around 2 times in around 2 years (on a desktop box - gcc 4.1.1, X 7.1.1 etc.), and that's only because i didnt read the migration guide. People who dont update their system often may run into problems too, but thats their fault, like all OS' you should it up to date. Also if you experience problems its also likely caused by running the unstable Gentoo packages, ie. ~amd64/~x86 which isn't recommended. - guigouz, on 10/12/2007, -0/+1ebuild /path/to/file.ebuild digest also, but as I said earlier, I'm using a "stable" tree. Things like these should not happen.
- isolationism, on 10/12/2007, -0/+1You're entitled to your own experience as am I -- and I'm speaking from my own, personal experience when I say Gentoo's compilation toolchain has broken often enough for me to not want to be maintaining it on a desktop if a good alternative exists.
Maybe the fact that I'm using AMD64 has something to do with it, but I don't know and it doesn't really matter, does it? Because every other major distro out there now supports AMD64, too -- and I haven't had to trawl forums to figure out how to upgrade anything successfully on Ubuntu. I press a button, and it happens, whether it's a package, library, or kernel update.
Incidentally, to those stating that the upgrade docs will steer you right every time, I would like to assert two points:
First, even following the docs does not guarantee a smooth upgrade process -- because your system could be in any number of states with any number of package versions installed at the time of an upgrade. While there are dependency trees designed to resolve these package versions, they aren't always accurate or up-to-date. Any search for basic toolchain libraries on the Gentoo boards or bug tracker will turn up more than enough hits to prove this point.
Second, I didn't distinguish between installing "any" software package and glibc/gcc because Gentoo doesn't make any distinction, either -- they're all 'world' packages, and as far as I'm concerned, letting you simply type "emerge world" when the action WILL break your system if you haven't established that fact ahead of time is idiotic and you should know better -- That is what masking is for, and why there are so many tiers of package masking in Gentoo. Ergo: If the upgrade operation isn't virtually guaranteed to go smoothly without user action/intervention, why the hell is it not masked?
Last but not least, you'll notice in the recent Slashdot thread on the topic of the "10-day Gentoo install" that I am far from being the only Gentoo user with similar experiences regarding updating the OS. Anyone who wants a bit of a broader span of opinions on the subject might wander over to read a few of the user comments there. - pdiddle, on 10/12/2007, -0/+1if you have a package with the wrong md5 digest, re-emerge it like so:
emerge --digest - Javock, on 10/12/2007, -0/+0I don't know what you are talking about!
I manage 4 gentoo's, 2 servers and 2 workstations and I almost everyday emerge world on the desktops, and once a week on the servers (yeah, I know, I am sick :))... I find that I break my system not often, and only when there is a *major* (libc, gcc) update there is a chance to get things really screwed up, but the gentoo docs are clear and almost always guide you to a successful emerge... My advise is that you (or anyone) keep an eye on the docs, and also watch for the emerge messages.
Regards! - serend, on 10/12/2007, -7/+2@isolationism
emerge world huh? if you knew what you were doing, like emerge -e world and not running dispatch-conf correctly you may have this happen. so why dont you learn what your talking about and do an emerge -C gcc glibc portage for me okay - coastie, on 10/12/2007, -5/+0This link goes to a bug tracker? is there an article?


What is Digg?
Digg is coming to a city (and computer) near you! Check out all the details on our