Re: [kde-linux] sourceforge vs. Konqueror
- Date: Wed, 11 Jan 2012 09:24:28 +0000 (UTC)
- From: Duncan <1i5t5.duncan@xxxxxxx>
- Subject: Re: [kde-linux] sourceforge vs. Konqueror
James Tyrer posted on Tue, 10 Jan 2012 19:30:34 -0700 as excerpted:
> On 01/09/2012 09:18 AM, Duncan wrote:
>> James Tyrer posted on Mon, 09 Jan 2012 06:03:32 -0700 as excerpted:
>>>> I decided it was time to upgrade gcc from the 4.5 series to the 4.6
>>>> series (4.6.2), and rebuild my entire system with the new gcc but
>>>> upgrading to the new kde at the same time, so I wouldn't end up doing
>>>> it twice.
>>> Sounds like a lot of fun. I have to admit that I do not rebuild
>>> everything when I upgrade the compiler.
>> AFAIK it used to be more or less required, especially for pretty much
>> anything C++
> This used to be the case for everything that was C++ since new versions
> of libstdc++ were, as you said, not compatible. It is still probably a
> good idea to immediately rebuild the C++ stuff, but it is no longer
> I usually go through an upgrade stuff rather than recompiling the
> existing versions.
Well, I do that too, except that gentoo is a rolling release and I update
frequently enough that it's mostly rebuilds. Which does make tracing
problems eaiser since I know for sure that it built and was working with
the old gcc, that way.
But the biggest set of updates I do all at once is definitely kde, IIRC
190-ish package builds out of 930 installed, now that I have the semantic-
desktop options turned off and am not building any kdepim apps at all
since the big akonadification, so doing that upgrade as part of the
rebuild does avoid having to build those packages twice, usually plus
another perhaps a half dozen to a dozen non-kde package updates since my
last system update.
> I note that one of these would be: "clucene-core-188.8.131.52" which was
> finally released. I checked and the current version of KDE-4.8 RC2 will
> build against it.
Hmm... I have that installed already here. Looks like gentoo added it
back on 12 Nov so I probably had it installed before 4.7.80 aka 4.8-
beta1, which according to the kde release schedule on techbase was
released on 23 Nov. Actually, I pretty well KNOW I did, since the date
on my copy of the sources tarball is 15 Nov.
And here I was thinking there was a fresh release that Gentoo and thus I
might be missing, since I didn't remember clucene being in my update list
(so it'd have been a rebuild) when I did the -rc2 update, since you said
I think what you must have /really/ meant was that you're "finally"
getting around to installing it! What took you so long? =:^)
(OTOH it's not marked gentoo arch-stale^H^Hble yet. Only ~arch. But
stale's for people who want just that, stale, since standard gentoo
stabilization time is 30 days without a stabilization blocker bug-report,
which mean's stale users are by definition at least 30 days stale on
almost their entire system! With some packages including KDE with its
monthly bugfix release cycle, that mean's gentoo/stable is NEVER on
upstream-current and thus ALWAYS stale, since by the time gentoo
stabilizes a particular version, a more current new upstream version has
already been released!)
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
This message is from the kde-linux mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde-linux.
More info: http://www.kde.org/faq.html.