| 1 |
On Saturday, 30 May 2020 19:08:13 BST Neil Bothwick wrote: |
| 2 |
> On Sat, 30 May 2020 18:44:02 +0100, Peter Humphrey wrote: |
| 3 |
> > I masked the latest version of plasma-meta, 5.18.5, when it appeared |
| 4 |
> > last week, because it insisted on installing network-manager, which I |
| 5 |
> > neither need nor want. Now I'm running an emerge -e @world, and portage |
| 6 |
> > insists on plasma- meta-5.18.5. (Why?) If I unmask it, network-manager |
| 7 |
> > insists on wifi ( wext ? Wifi ) even though there's no such hardware on |
| 8 |
> > this machine. |
| 9 |
> > |
| 10 |
> > For the moment I've excluded plasma-meta from the -e @world, which |
| 11 |
> > seems to be doing the job. |
| 12 |
> |
| 13 |
> The point of meta packages is that they install a whole set of stuff, in |
| 14 |
> this case "Merge this to pull in all Plasma 5 packages". If you don't want |
| 15 |
> the kitchen sink, don't use meta packages. I have a kde set in /etc/ |
| 16 |
> portage/sets that includes just what I want. As a result I have a decent KDE |
| 17 |
> desktop but without needing networkmanager, or any of the PIM stuff. |
| 18 |
|
| 19 |
I tried doing that some time ago. I got so heavily bogged down in a dependency |
| 20 |
mire that I gave up. You wouldn't like to show your set, would you? Please? :) |
| 21 |
|
| 22 |
-- |
| 23 |
Regards, |
| 24 |
Peter. |
Archives