On Mon, Feb 20, 2017 at 01:44:02PM +0100, Kai Krakow wrote
> You could also try to stop portage from even syncing the KDE components
> into the tree. I usually do this for small systems to not give portage
> any chance of pulling in unwanted components. As a plus, syncing and
> dep calculation
On Monday 20 Feb 2017 15:32:25 Grant Edwards wrote:
> On 2017-02-19, Mick wrote:
> >> And what pulls in NetworkManager? KDE's power manager with USE=wireless!
>
> I despise NetworkManager. Over the years, it has been the cause of
> countless problems and hours of
"Walter Dnes" writes:
[...]
> 1) "eselect profile list" and switch to a basic non-KDE profile of your
> choice.
Moved from:
default/linux/amd64/13.0/desktop *
to
default/linux/amd64/13.0 *
>
> 2) "emerge gentoolkit" if not already present.
>
> 3) "cat
On 2017-02-19, Mick wrote:
>> And what pulls in NetworkManager? KDE's power manager with USE=wireless!
I despise NetworkManager. Over the years, it has been the cause of
countless problems and hours of wasted time. The first I do when
dealing with network problems
Am Sat, 18 Feb 2017 22:05:01 -0500
schrieb "Walter Dnes" :
> On Sat, Feb 18, 2017 at 04:57:52PM -0500, Harry Putnam wrote
>
> > Any advice about slick ways of getting fully updated but dumping kde
> > on the way.
>
> *IMPORTANT* KDE is obscene about dependancies.
5 matches
Mail list logo