From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Update blocked by kdebase-startkde:4
Date: Sat, 09 Jul 2016 23:40:31 +0100 [thread overview]
Message-ID: <2616034.iRykjQo1re@peak> (raw)
In-Reply-To: <2260081.eQf0LrpUZy@peak>
On Saturday 09 Jul 2016 23:22:49 I wrote:
> On Sunday 10 Jul 2016 04:08:36 Michael Palimaka wrote:
--->8
> > This change is correct - we're in the process of cleaning up some old
> > ebuilds at the moment.
> >
> > In this case kde-apps/kdebase-runtime-meta:5 doesn't imply anything
> > KF5-based - it has just been ported to use a newer eclass. It still just
> > pulls in the old KDE4-based kde-runtime packages.
I don't think that's entirely true; see below.
> That's good news. Now, how does one allow that package to be installed while
> keeping the rest of KF5 masked?
>
> # cat /etc/portage/package.mask
> kde-plasma/*
> kde-frameworks/*:5
> kde-apps/*:5
> kde-misc/*:5
> >=kde-apps/kde4-l10n-16.04.1
>
> We seem to need an analogue of CONFIG_PROTECT and CONFIG_PROTECT_MASK, in
> which we could mask all kde-apps/*:5 while allowing
> kde-apps/kdebase-runtime-meta:5 to be installed. Can that be done? I hope
> there's an easier way than masking all 122 apps separately.
In fact I tried the separate masking. It led on to having to treat kde-plasma
and kde-frameworks similarly, and before I knew it I was unmasking a load of
packages that don't belong in a KDE-4 system.
What to try next?
--
Rgds
Peter
next prev parent reply other threads:[~2016-07-09 22:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 13:52 [gentoo-user] Update blocked by kdebase-startkde:4 Robin Atwood
2016-07-09 16:10 ` Peter Humphrey
2016-07-09 18:08 ` [gentoo-user] " Michael Palimaka
2016-07-09 22:22 ` Peter Humphrey
2016-07-09 22:40 ` Peter Humphrey [this message]
2016-07-09 23:30 ` Daniel Frey
2016-07-10 2:08 ` Peter Humphrey
2016-07-10 2:45 ` Daniel Frey
2016-07-10 11:22 ` Peter Humphrey
2016-07-10 16:00 ` Daniel Frey
2016-07-10 17:43 ` Neil Bothwick
2016-07-10 17:55 ` Alan McKinnon
2016-07-11 12:57 ` Peter Humphrey
2016-07-11 10:16 ` [gentoo-user] " Jörg Schaible
2016-07-10 11:17 ` [gentoo-user] " Peter Humphrey
2016-07-10 13:17 ` Robin Atwood
2016-07-11 21:30 ` [gentoo-user] " Andrés Becerra Sandoval
2016-07-15 14:59 ` Robin Atwood
2016-08-13 13:56 ` Robin Atwood
2016-08-13 14:58 ` Peter Humphrey
2016-08-13 15:54 ` Robin Atwood
2016-08-14 8:20 ` Peter Humphrey
2016-08-14 12:12 ` Robin Atwood
2016-08-14 13:28 ` Peter Humphrey
2016-08-14 16:20 ` Daniel Frey
2016-08-14 17:17 ` Robin Atwood
2016-09-17 13:26 ` Robin Atwood
2016-09-17 14:18 ` Alan McKinnon
2016-09-17 15:16 ` Robin Atwood
2016-09-17 19:08 ` Alan McKinnon
2016-09-17 19:17 ` Daniel Frey
2016-09-17 19:26 ` Alan McKinnon
2016-09-18 14:55 ` Robin Atwood
2016-09-19 18:22 ` konsolebox
2016-09-21 15:14 ` Robin Atwood
2016-08-13 15:47 ` Daniel Frey
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=2616034.iRykjQo1re@peak \
--to=peter@prh.myzen.co.uk \
--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