From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: has anyone tried KDE5?
Date: Wed, 08 Oct 2014 19:38:57 +0200 [thread overview]
Message-ID: <543576B1.9050307@googlemail.com> (raw)
In-Reply-To: <m131ou$2n8$1@ger.gmane.org>
Am 08.10.2014 um 11:56 schrieb Michael Palimaka:
> On 10/08/2014 07:31 AM, Volker Armin Hemmann wrote:
>> so after spending hours fighting to upgrade boost, I finally got to the
>> point were portage let me emerge kde-framework.
>>
>> I went to bed.
>>
>> I woke up 2h later... only 9 packages were installed, the rest skipped
>> because of wrong gcc.
>>
>> Crap like that should be told right at the start.
> This is carryover from KDE 4. In all packages except kdelibs, the GCC
> check was in pkg_setup instead of pkg_pretend to save time during
> dependency resolution (think emerging 300 KDE packages at once).
>
> I did some quick tests and I'm not convinced that the small time saving
> justifies bending the rules and causing the sort of issue you ran into.
>
>
>
luckily, I did have gcc 4.8 installed, until now I just did not have a
reason to switch. Afterwards emerging the rest was a non-issue. emerge
@preserved-rebuild is not happy, of course because of kactivities-4 and
-5 not liking each other.. let them be unhappy...
next prev parent reply other threads:[~2014-10-08 17:39 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 13:26 [gentoo-user] has anyone tried KDE5? behrouz khosravi
2014-10-04 17:37 ` [gentoo-user] " Michael Palimaka
2014-10-05 13:17 ` Tanstaafl
2014-10-05 15:01 ` Michael Palimaka
2014-10-05 15:35 ` Tanstaafl
2014-10-05 15:50 ` Michael Palimaka
2014-10-05 16:27 ` Alan McKinnon
2014-10-05 16:59 ` Volker Armin Hemmann
2014-10-05 17:10 ` Alan McKinnon
2014-10-05 17:25 ` Volker Armin Hemmann
2014-10-07 7:24 ` [gentoo-user] " Pavel Volkov
2014-10-07 14:48 ` Philip Webb
2014-10-07 15:20 ` Mick
2014-10-07 17:27 ` Philip Webb
2014-10-07 18:26 ` J. Roeleveld
2014-10-07 19:20 ` Daniel Frey
2014-10-08 4:42 ` J. Roeleveld
2014-10-09 3:32 ` Daniel Frey
2014-10-14 5:50 ` J. Roeleveld
2014-10-14 19:22 ` Daniel Frey
2014-10-14 20:16 ` Alan McKinnon
2014-10-16 17:06 ` Daniel Frey
2014-10-07 20:18 ` Neil Bothwick
2014-10-07 21:32 ` Mick
2014-10-08 6:45 ` Pavel Volkov
2014-10-08 7:32 ` J. Roeleveld
2014-10-08 8:11 ` Neil Bothwick
2014-10-08 4:46 ` J. Roeleveld
2014-10-08 5:29 ` Mick
2014-10-08 7:30 ` J. Roeleveld
2014-10-09 17:44 ` Francisco Ares
2014-10-09 19:38 ` Alan McKinnon
2014-10-09 20:01 ` Volker Armin Hemmann
2014-10-11 9:45 ` Mick
2014-10-06 15:44 ` [gentoo-user] " Jens Reinemuth
2014-10-06 21:47 ` Mick
2014-10-07 5:02 ` J. Roeleveld
2014-10-07 6:48 ` Jens Reinemuth
2014-10-05 18:34 ` Volker Armin Hemmann
2014-10-06 9:57 ` Michael Palimaka
2014-10-06 15:55 ` Volker Armin Hemmann
2014-10-07 20:31 ` Volker Armin Hemmann
2014-10-08 9:56 ` Michael Palimaka
2014-10-08 17:38 ` Volker Armin Hemmann [this message]
2014-10-09 7:56 ` Michael Palimaka
2014-10-09 15:40 ` Volker Armin Hemmann
2014-10-07 7:41 ` [gentoo-user] " Pavel Volkov
2014-10-07 9:21 ` [gentoo-user] " Michael Palimaka
2014-10-12 12:11 ` Stefano Crocco
2014-10-12 15:20 ` Michael Palimaka
2014-10-12 18:45 ` Stefano Crocco
2014-10-05 12:19 ` [gentoo-user] " Paige Thompson
2014-10-05 12:20 ` Paige Thompson
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=543576B1.9050307@googlemail.com \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@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