

Are you actually serious?Zork the Almighty wrote:Add to that the developer's tendency to introduce deep structural changes to the system on a continuous basis. I don't mind that Gentoo in 2006 uses udev instead of devfs, and Xorg instead of the standard X11. Certainly we all have to make these changes. What I dislike is the fact that these types of changes are made every two or three months, and often before the new software is ready. Sometimes the "solution" is to install a bunch of packages from ~x86, weeks before they are made "stable". What does that say ?
You know the end result is the same as before, right? They're just installed in smaller chunks? If anything it's leaner and meaner this way...Zork the Almighty wrote:Instead of 10 packages for KDE we have 200, and instead of 1 package for X we have 100

so one more prophet of disaster - a real pandemonium in recent times (it seems it is contagious - so don't read"O God of Earth and Altar,
Bow down and hear our cry,
Our earthly rulers falter,
Our people drift and die,
The walls of gold entomb us,
The swords of scorn divide,
Take not thy thunder from us,
But take away our pride."
(G. K. Chesterton; English Hymnal)
That's something I totally agree with -- I tried keeping my system as stable and basic as possible, but random breaks grew my file that holds unmaksed packages longer and longer for some reason...Zork the Almighty wrote:Sometimes the "solution" is to install a bunch of packages from ~x86, weeks before they are made "stable".


+1Lechium wrote:That's something I totally agree with -- I tried keeping my system as stable and basic as possible, but random breaks grew my file that holds unmaksed packages longer and longer for some reason...Zork the Almighty wrote:Sometimes the "solution" is to install a bunch of packages from ~x86, weeks before they are made "stable".

Yes, because unstable packages can require unstable packages. Why is that surprising?Lechium wrote:That's something I totally agree with -- I tried keeping my system as stable and basic as possible, but random breaks grew my file that holds unmaksed packages longer and longer for some reason...Zork the Almighty wrote:Sometimes the "solution" is to install a bunch of packages from ~x86, weeks before they are made "stable".
The KDE4 build system is changing, and the monolithic builds are still around for your convenience. Xorg is now modular. Both cases, this was an upstream decision. Net result? Shortened build time once it's up and running. The packages that actually get updated during the point releases are rebuilt and the packages unchanged are left alone.Fast-forward to today, where the current fad seems to be "modular packages". Instead of 10 packages for KDE we have 200, and instead of 1 package for X we have 100, and something is updated every day.
Things that change drastically have advanced notice on the forums, and gentoo weekly news (and probably mailing lists). Along with the notice comes a guide in how to upgrade smoothly. Xorg modular has one. GCC upgrade has one. The new java system has one. The Apache shift around 2.0.50 had one. Most cases this is updating some config files and then waiting for them to build.Add to that the developer's tendency to introduce deep structural changes to the system on a continuous basis.


You've clearly misunderstood what it said and what he meant. Many ebuilds in stable (x86) are not properly made, so either one has to try to fix the ebuild by oneself, or try a newer unstable package which might work. It has nothing to do with unstable, it's just that stable isn't stable as one would want it to be.antonlacon wrote:Yes, because unstable packages can require unstable packages. Why is that surprising?

So do I. Gentoo runs as fast and smooth as it did the first time I installed itgentoo_lan wrote:Most of what you said I disagree with

Which is the case with modular KDE and Xorg. I bet there are not many people in the world who wouldShadow Skill wrote:Modularity is only a problem when you end up actually needing 50 of the 100 packages to get relatively basic functionality out of an app or given set of apps other than that modularity is a very good thing.

I try to avoid these ranting posts as much as possible, but every hundred or so I figure I might as well throw in my 2 cents for the google search bot to read and catalog.Zork the Almighty wrote: The only people who can seem to maintain the system are its developers, and trying to "use" Gentoo is the craziest thing I have ever seen a large group of people do.
Which packages would you prefer weren't in portage? Name one and I bet a dozen people would complain that their favourite xxx was missing.Zork the Almighty wrote:It took 5 seconds to update the portage cache.
Modularisation is exactly the thing that helps you to keep unwanted packages off your system. You're complaining about the very thing that helps to solve the very issue that you're complaining about. And as others have said, this choice has little to do with Gentoo.Zork the Almighty wrote:Fast-forward to today, where the current fad seems to be "modular packages". Instead of 10 packages for KDE we have 200, and instead of 1 package for X we have 100, and something is updated every day. There are now so many possible configurations, depending on whether you last updated a day, a week, or a month ago, that it is pointless to try to test anything.
We all do our best to help when things break, but I can't agree with that statement. In the past 2 years I've only had 1 show-stopping update, and that was sorted by emerge --sync, and emerge the offending package (udev if I remember correctly).Zork the Almighty wrote:The software is simply thrown onto the users, and whatever is broken is sorted out in the forums.
Would you prefer that Gentoo didn't progress, still used Kernel 2.2, TWM, devfs. You'd have a hard time finding many people to agree with you.Zork the Almighty wrote:Add to that the developer's tendency to introduce deep structural changes to the system on a continuous basis.
I take it you're talking about the switch to xorg 7.0. When I read the migration guide it did strike me as odd that I would have to umask some packages to update. I delayed a bit (about 3-4 weeks) to make the change, and when I did, there was nothing to unmask at all, and that's on AMD64.Zork the Almighty wrote:What I dislike is the fact that these types of changes are made every two or three months, and often before the new software is ready. Sometimes the "solution" is to install a bunch of packages from ~x86, weeks before they are made "stable". What does that say ?
Why update then if your system works OK. Pesonally I run emerge -u world weekly and emerge -uD world monthly, and have no problems. Takes <1hour per week, unless there's a big change like KDE, xorg or gcc.Zork the Almighty wrote:The bottom line is that I go out of town for one month, and when I return I spend one or two full days updating and repairing my system. It's not just compile time - I may as well reinstall. In fact, if you don't update you will be forced to reinstall because your configuration will quickly become unsupported, or updating it will break it beyond all repair.
Sure, updating a system does leave stuff lying around, taking up disk space, but, unlike Windows, doesn't affect the speed of the system.Zork the Almighty wrote:There are so many packages now that it becomes impossible to strip out bloat. When one piece of software requires 100 packages, someone in that list will always want to install Gnome or Ruby or GTK+ or some other unnecessary dependency. Bloat is also added whenever the underlying system is changed, because new dependencies are added and old ones are not removed. I know there are tools for detecting this, but I also know that they don't often work. I'm pretty sure that if I reinstalled Gentoo right now I could build a lean and modular system, but a year later it would be spaghetti again.
Not having used any other distros for a long time, but doesn't that mean a full re-install every 6 months or so? How is that better than Gentoo? What if your favourite package has a major update just after your distro is released. You either have to wait for the next distro version or go through RPM hell.Zork the Almighty wrote:Most distributions cherry pick the best versions of software for a "release", and then actually test the software (in a "beta" version) to see if it works. This way the users get the benefits of a fairly modern house, with only periodic interuptions instead of continuous construction.
Well I'm not a developer, have no coding experience and have no difficulty maintaining my two Gentoo PCs, one running x86 and the other AMD64Zork the Almighty wrote:The only people who can seem to maintain the system are its developers, and trying to "use" Gentoo is the craziest thing I have ever seen a large group of people do.


If you think 15 minutes is too much of your time for repairing minor breakages, you are just being difficult. No matter how 'busy' one claims to be, 15 minutes isn't a lot of time. Agreed, everyone would do well without the breakage occurring in the first place, but a system upgrade of that magnitude over the net is a difficult thing to achieve.Zork the Almighty wrote: In the last three months I have updated my machine three times, and every time something seriously broke (ie: it took more than 15 minutes of my time). In one instance the device files in /dev which were previously tarred and restored were no longer tarred and restored after an update, which broke X11's video and mouse config. The new Nvidia drivers also had some sort of crazy problem. I was forced to update the system because my profile (from 2005) would not be supported any longer, meaning I would not be able to update at all and I would have to reinstall.
The udev update was a fundamental system change, and yes, should have been highlighted more prominently. I wasn't around back then and I don't know if a proper list of steps to attempt a safe upgrade, like gcc upgrades, was made available at the time.Zork the Almighty wrote: My criticisms of udev, modular KDE and Xorg, etc, are not meant to say Gentoo should not make those changes. But some sort of announcement or schedule is needed for major updates. The update to udev, for example, took me completely by surprise. You can't always tell when an update is a major update that has the potential to break your system. On more than one occasion I thought "I'll just update this minor thing before I go to bed" and then BOOM! I was up all night trying to make sure the system would boot up in the morning when my wife needed to use it. The fact is, every time I update the system I have to set aside time because of the potential for major hassles. For modular KDE, I didn't even bother. All that trouble for what, KDE 3.5 ? It would have been better to save that change for KDE 4.0, which is guaranteed to be a massive problem anyway.
But you know that from the time you install gentoo. It IS a source based disribution, hence the long compile times for a system wide upgrade. Also, if it is such a problem, you may consider cross compiling or just patching vulnerable programs rather than a full system update. Agreed, it would take a bit of work, but that is what you get with a source based distribution.Zork the Almighty wrote: The change to modular Xorg at least coincides with a major version number, and ultimately, it makes sense, but I can't help thinking it would be less trouble to reinstall. Unfortunately my processor is a little slow these days, and although I use tmpfs for compiling (best tip ever!) it still takes 12-18 hours to get everything set up. BTW, another good trick I find is to stick the portage tree on /var on a separate partition. It avoids fragmentation, but also too many partitions. You can delete distfiles and even most of the ebuilds to gain free space on /var if you ever need it.
This is not just a problem with Gentoo. Lots of distros, even binary ones, experience breakage quite often while updating over the net. It is usually a consequence of most people having different configurations, and the update fails to consider all cases in which this could occur.Zork the Almighty wrote: So basically, my only real gripe with Gentoo is that I'm getting really tired of things breaking. I don't mind if things break for major updates, even if it's multiple things at once. But it's really annoying to have it happen every month or so, when you least expect it. Maybe my system has just lasted longer than usual (I last reinstalled in late 2004) and nobody else is experiencing these problems, but if that's the case then it is a serious issue (and one of the reasons why I hate Windows).
MacOSX is nothing brilliant. People do not experiment with it as much as they do with Linux. And most machines running OSX have a more or less similar system state while attempting an upgrade. So that approach works there.Zork the Almighty wrote: In a larger context, I think the whole "package management" system that Linux uses is broken. I would prefer a distro that had Desktop and Server base installs, and otherwise statically compiled apps with few dependencies (only big things, like Gnome or KDE). With i686 builds and prelinking the speed difference is gone, and although it's interesting to construct a system with no bloat, you can't maintain it for reasons I posted earlier. I think Linux should try as much as possible to copy Mac OS X (before Apple wrecks it). It's far from perfect (don't look under the hood), but its approach to installing applications is correct.
Heh. Now you really are joking. Try a system wide FreeBSD update sometime. For an OS that has the core system and the kernel so tightly tied together, it still throws up breakage problems. Although the updates do not come as thick and fast as with Gentoo, they are still not without their fair share of problems.Zork the Almighty wrote: Otherwise, FreeBSD offers a good model. Gentoo is very close to FreeBSD in many ways, however the difference is that FreeBSD has releases, and the fundamentals of the system don't change outside of those. You can upgrade things and they basically don't break. On the Linux side, Slackware is often compared to BSD, and it is the distro I will probably try next (when version 11 is released). I've used it before to breathe life into an old notebook computer, and although I find their defaults too conservative (2.4 kernel !?) you do at least get a stable, no-nonsense system. My only concern is that it will quickly get stale, at which point I will have to reinstall Gentoo![]()