On Saturday 27 May 2006 19:58, Alexander Skwar wrote: > Richard Fish wrote: > > On 5/27/06, Alexander Skwar <[EMAIL PROTECTED]> wrote: > >> gcc update "Nothing needs to be done".... Sure... How much did the > >> person who wrote this check? "Hello World!" worked, and that's it? > >> > >> 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. >
no it does not. You are talking bullshit. GWN: The number of applications that do not compile with gcc-4.1 is extremely small now, and most users should not experience any problems with ~arch packages not compiling. Read it, understand it. It is hard, I know. But it does not say 'riskless'. Not even 'basically riskless'. Read again. And the uzpgrade guide says: Generally speaking, upgrades to bug fix releases, like from 3.3.5 to 3.3.6, should be quite safe -- just emerge new version, switch your system to use it and rebuild the only affected package, libtool. However, some GCC upgrades break binary compatibility; in such cases a rebuild of the affected packages (or even whole toolchain and system) might be required. > > ~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. > > 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. > and ~arch is the testing ground. Basic testing 'it works or it works not' are the hard-masked packages. Maybe you should calm down? Or do you want to stay in your sulk-mode and act like a prima donna? > And what's also irritating are so many small errors, like files > with non-matching filesizes/checksums in the digests. > > > 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? > > Then you're experiences just don't count. KDE broke on my > system, when I recompiled Qt. Before the recompile, KDE was fine. > As I've wrote in lengths on the bug report. Seems you've not read > it - why not? Why am I writing reports and *also* post links > here? > oh, that is sooo surprising. Most of the times, a qt-update requires recompiling kdelibs, base and network (and kdepim). Something that happens even without gcc-updates. > Did you try to compile glib? No? Then I guess you've done no testing. if he does not have glib? > Or what kind of testing have you done? enough for his system? > > > Since these are all heavy > > C++ users, I am sure that for my (pure ~x86) system, there are no > > issues. > > Congrats. It's not only me who's having problems. > no, you are not the only one, but you are one who makes a lot of fuss about problems, that are easy to solve and even happen without any gcc updates - and you should have learnt to deal with a long time ago. -- gentoo-user@gentoo.org mailing list
