From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 397BD1382FE for ; Sat, 9 Jul 2016 22:40:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9A978E0BE9; Sat, 9 Jul 2016 22:40:33 +0000 (UTC) Received: from smarthost03d.mail.zen.net.uk (smarthost03d.mail.zen.net.uk [212.23.1.23]) by pigeon.gentoo.org (Postfix) with ESMTP id 73FE4E09C5 for ; Sat, 9 Jul 2016 22:40:32 +0000 (UTC) Received: from [82.69.80.10] (helo=peak.localnet) by smarthost03d.mail.zen.net.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1bM0vH-00056Z-GX for gentoo-user@lists.gentoo.org; Sat, 09 Jul 2016 22:40:31 +0000 From: Peter Humphrey 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 Message-ID: <2616034.iRykjQo1re@peak> User-Agent: KMail/4.14.10 (Linux/4.6.3-gentoo; KDE/4.14.21; x86_64; ; ) In-Reply-To: <2260081.eQf0LrpUZy@peak> References: <201607092052.46760.robin@binro.org> <2260081.eQf0LrpUZy@peak> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost03d-IP: [82.69.80.10] X-Archives-Salt: b8929bbc-1580-47ff-aa4f-43747065e95f X-Archives-Hash: 22755569e86cd19c2d8ef7c9bf315c48 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