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
