public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: move to xfce and forget kde and gnome
Date: Mon, 22 Aug 2011 07:30:55 -0400	[thread overview]
Message-ID: <CA+czFiDJr3WiM1ja90HyVNQqu3_6d5tWou2Ds9w4q=W7=eJqvA@mail.gmail.com> (raw)
In-Reply-To: <4E522596.60806@gmail.com>

2011/8/22 Space Cake <spacecakex@gmail.com>:
> 2011-08-19 14:54 keltezéssel, Nikos Chantziaras írta:
>> On 08/19/2011 03:02 PM, Space Cake wrote:
>>> hi,
>>>
>>> after playing a lot with desktop environment first I've decided to move
>>> from kde to gnome because kde is too "shine" and eat too much and
>>> contains a lot of feature which I don't really need.. gnome is good but
>>> still too fat.... so finally I've found Xfce which is perfect for my
>>> needs... :)
>>>
>>> my question is what is the easiest way to get rid of kde/gnome stuff? is
>>> this enough to change my useflags to -kde and -gnome? Is there any list
>>> what I can safely unmerge in this case?
>>
>> You change your profile.  You can see your current profile with:
>>
>>   eselect profile list
>>
>> For KDE you would use "default/linux/amd64/10.0/desktop/kde" and for
>> Gnome "default/linux/amd64/10.0/desktop/gnome".
>>
>> For anything else, use "default/linux/amd64/10.0/desktop".  Then do a:
>>
>>   emerge -auDN --with-bdeps=y world
>>   emerge -a --depclean
>>
>> If KDE/Gnome stuff still remains after that, use:
>>
>>   emerge -pv --depclean <package>
>>
>> to see what's pulling-in <package>.
>>
>>
> So, what if I have changed the flags to -kde and -gnome, and I also ran
> depclean, also used the script provided by some kind member of the list
> and I still have all the kde gnome stuff on my system? Do I need some
> list of packages should I unmerge? Should I simple unmerge packages
> kde-base/* and so on and run revdep-rebuild after this? Is this a
> working approach?

I just cleaned off KDE (and PulseAudio, as it happens) from my system
Saturday night/sunday morning. I wasn't using the KDE profile.

Here are the steps I followed:

1) Remove all 'kde' and 'qt' USE flags from make.conf. (I didn't have
to remove qt, but I preferred to switch over to package-specific
support for it, as needed, rather than global)
2) emerge --depclean (pretend first, then add anything I *knew* I
didn't want to lose to @world, then pretend again, until there wasn't
anything that would be removed I wasn't comfortable with)
3) If there were any KDE packages left, emerge -pPv on them, to find
what was pulling them in. "emerge --deselect" the packages that were
pulling the KDE packages in. (Sometimes, this would involve supplying
an alternative. For example, I had to emerge Awesome before it would
remove knotify.)
4) Jump back to step 2, unless I couldn't get a package to disappear
with --depclean.
5) revdep-rebuild (in my case, only a Jack library was busted)
6) emerge --deep --newuse --keep-going world && emerge --sync &&
emerge --update --deep --newuse --keep-going world # This part, I left
running overnight. It succeeded, to my surprise.

I did have a couple recursive-dependency-like situations. For example,
KDE has a policykit agent, which depends on polkit. The policykit
agent wouldn't go away; emerge -pPv said polkit was pulling it in, and
said that the agent was what was pulling polkit in. In those
situations, I found I had to --unmerge a piece of the dependency loop
in order for emerge to allow it to go away or get replaced. In the
polkit case, I removed the KDE agent.

I also had to remove a few packages I do occasionally use, because
they were pulling in Qt or KDE. In particular, I --deselect'd calibre.
I've still got qt libs on my system, though, because I use
Luminance-HDR a *lot*.

I found it surprisingly painless. Note, I went through most of these
steps with X *NOT* running; I switched to a terminal and stopped kdm
before really going past step 2.

-- 
:wq



  parent reply	other threads:[~2011-08-22 11:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 12:02 [gentoo-user] move to xfce and forget kde and gnome Space Cake
2011-08-19 12:54 ` [gentoo-user] " Nikos Chantziaras
2011-08-19 14:07   ` Space Cake
2011-08-19 14:27     ` jdm
2011-08-19 14:41       ` Nikos Chantziaras
2011-08-19 14:39     ` Nikos Chantziaras
2011-08-19 16:03   ` Peter Humphrey
2011-08-22  9:47   ` Space Cake
2011-08-22 10:32     ` Neil Bothwick
2011-08-22 11:30     ` Michael Mol [this message]
2011-08-22 17:08       ` Michael Mol
2011-08-19 14:50 ` [gentoo-user] " András Csányi
2011-08-19 15:19   ` Space Cake
2011-08-19 23:14     ` Walter Dnes
2011-08-20  0:34       ` Peter Humphrey
2011-08-20  4:02         ` Walter Dnes
2011-08-20  8:07           ` Alan McKinnon
2011-08-20 10:32             ` Peter Humphrey
2011-08-20  1:17       ` Pandu Poluan
2011-08-20  4:10         ` Walter Dnes
2011-08-19 19:54   ` Daniel da Veiga

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='CA+czFiDJr3WiM1ja90HyVNQqu3_6d5tWou2Ds9w4q=W7=eJqvA@mail.gmail.com' \
    --to=mikemol@gmail.com \
    --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