From: Michael Mol <mikemol@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RANT: Upgrade icu and KDE at once
Date: Tue, 30 Apr 2013 13:17:36 -0400 [thread overview]
Message-ID: <517FFCB0.5060802@gmail.com> (raw)
In-Reply-To: <CAGfcS_=RSw-Tmt+q9rLkarsyhSjZ1=1P8FRnsGm1rQgkyyNrLg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On 04/30/2013 01:06 PM, Rich Freeman wrote:
> On Tue, Apr 30, 2013 at 12:51 PM, Jörg Schaible <joerg.schaible@gmx.de> wrote:
>> The most annoying fact is, that none of this would have been necessary with
>> portage 2.2, but maybe we have to wait for 2.1.11.500 before 2.2 gets
>> stable...
>
> Actually, @preserved-rebuild is supported in the current stable
> portage. It just isn't the default or encouraged. I'm running stable
> portage and had no issues with the icu upgrade. It even triggered
> slot operator dependency rebuilds automatically for about a half-dozen
> packages.
>
> I did get the icu and KDE upgrades on separate days.
Indeed, the libicu update this time around went much, much cleaner than
any previous time. (At least, it did for me.)
I'm not running full KDE, though. The biggest quirk I hit, I described
in bug #468022
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
next prev parent reply other threads:[~2013-04-30 17:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 16:51 [gentoo-dev] RANT: Upgrade icu and KDE at once Jörg Schaible
2013-04-30 17:06 ` Rich Freeman
2013-04-30 17:17 ` Michael Mol [this message]
2013-04-30 17:24 ` Tom Wijsman
2013-04-30 18:02 ` Rich Freeman
2013-05-01 9:20 ` Peter Stuge
2013-05-01 9:42 ` Tom Wijsman
2013-05-01 10:29 ` Peter Stuge
2013-04-30 18:53 ` Zac Medico
2013-05-01 9:07 ` [gentoo-dev] " Jörg Schaible
2013-05-01 14:55 ` Zac Medico
2013-05-01 14:46 ` [gentoo-dev] " Mike Gilbert
2013-05-01 15:01 ` Zac Medico
2013-05-01 15:16 ` Mike Gilbert
2013-05-02 3:38 ` [gentoo-dev] " Duncan
2013-05-02 5:09 ` Tom Wijsman
2013-05-02 8:57 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=517FFCB0.5060802@gmail.com \
--to=mikemol@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox