Saturday 27 May 2006 19:58 skrev Alexander Skwar: > >> gcc update "Nothing needs to be done".... Sure... How much did the > >> person who wrote this check? "Hello World!" worked, and that's it?
What exactly do you intend to achieve by flaming the devs? > >> Sometimes this complete lack of QA is really pissing me off :( > > > > Stop using ~arch packages, or stop whining. > > No, I won't do neither. The GWN and the upgrade doc used to say, > that an upgrade is (basically) riskless. Well, you chose to be on the cutting edge. You chose to upgrade as soon as it was unmasked. If you really think there is a complete lack of QA then why the hell didn't you wait a week to see if it was true? > That's wrong - as it has been confirmed and corrected now. If that > warning would have been there in the gcc-upgrade doc, everything > would have been fine. > > > ~arch works most of the > > time, but it is a _testing_ branch. Do you expect the devs to login > > to each and every Gentoo user's system to test a new package and > > ensure complete functionality before adding it to ~arch? > > Bullshit. That's not bullshit. Occasional breakage is the risk when living on the cutting edge. This is the purpose of the testing branch. > I'd expect them to do testing and not give so bold statements > as "The upgrade should be incredibly easy and require no additional > work to install and use. " without making VERY sure, that this > is actually true. > > Granted - there's only so much that can be done. And also > granted, that's ~arch. But that statement is just so irritating. Well, the devs are unpaid volunteers and human beings. They do make mistakes sometimes but I'm quite convinced that their intensions are good. Get over it. > And what's also irritating are so many small errors, like files > with non-matching filesizes/checksums in the digests. This has got nothing to do with the gcc upgrade. It has to do with the fact that ebuilds are occasionally updated with no change of revision. > > I just upgraded to gcc-4.1 and pruned 3.4.6, and KDE, koffice, OOo, > > and mozilla all still load and run fine. > > Did you yet re-compile Qt 3 and Qt 4? No? I just did (only qt 3.3.6-r1 - I don't have qt 4). And guess what. KDE (kontact, kmail, knode, akregator, konqueror, ...) still works on my system. So now I'm recompiling everything that has the kdehiddenvisibility use flag with that enabled.. But did you not see the einfo from postinst in qt-3*? > INFO: postinst > After a rebuild of Qt, it can happen that Qt plugins (such as Qt/KDE styles, > or widgets for the Qt designer) are no longer recognized. If this situation > occurs you should recompile the packages providing these plugins, and you > should also make sure that Qt and its plugins were compiled with the same > version of gcc. Packages that may need to be rebuilt are, for instance, > kde-base/kdelibs, kde-base/kdeartwork and kde-base/kdeartwork-styles. > See http://doc.trolltech.com/3.3/plugins-howto.html for more infos. Note that it says rebuild and not upgrade. [SNIP] -- Bo Andresen
pgpLnvZ8Ai64G.pgp
Description: PGP signature
