On Sat, 24 Jun 2006 18:28:39 +0200, Bo Ørsted Andresen wrote:
You seem to have been more confused than enlightened by the tricks I
posted. If you want to nuke kde completely you should just do:
# cd /var/db/pkg emerge -Cva kde-base/*
You should also rm -fr /usr/kde or rm -fr
Bo Ørsted Andresen bo.andresen at zlin.dk writes:
The revdep-rebuild is good *after* emerging kde-meta. It will recompile third
party applications such as amarok against the new version of kde-meta. I
posted the simple steps at the bottom of my previous mail.
Assuming you really
do want
Bo Ørsted Andresen bo.andresen at zlin.dk writes:
On Thursday 22 June 2006 22:12, James wrote:
Ok I'll do this after emerging kde-meta completes. I hope I
was not suppose
to do this before 'emerge -uavDN kde-meta'
You weren't. Blocks are only within the same slot. In fact the
split
Your quoting style is terrible...!
On Saturday 24 June 2006 17:25, James wrote:
Unmerge what you don't need or remerge (after emerging kde 3.5) what
you still need. When you are done with that the above command should
give no output and any files still in /usr/kde/3.2 - 3.4 can be
Bo Ørsted Andresen bo.andresen at zlin.dk writes:
You weren't. Blocks are only within the same slot. In fact the split packages
blocks only the monolithic package they belong to.
Sorry, my last response got butchered. Gmane get's rediculous somethings
borderline upsurd on it's request to
On Saturday 24 June 2006 18:05, James wrote:
One of the KDE devs should put out a tool or script to completely
nuke kde, then let folks run
emerge -uavDN kde-meta' and be done with it. Disk space is cheap
and I do not have time to 'hack' at kde across 7 workstations.
Re compiling everything
Bo Ørsted Andresen bo.andresen at zlin.dk writes:
You seem to have been more confused than enlightened by the tricks I posted.
If you want to nuke kde completely you should just do:
# cd /var/db/pkg emerge -Cva kde-base/*
It's as simple as that. Both Neil and I told you that a long time
On Saturday 24 June 2006 19:21, James wrote:
Are these simple steps going to work?
If not please edit. I do not care about
extra compile time. I need a simple straightforward method
to nuke(unistall all of KDE) and install via kde-meta
First:#
nuke all occurances of kde
cd /var/db/pkg
Bo Ørsted Andresen bo.andresen at zlin.dk writes:
On Thursday 22 June 2006 18:28, James wrote:
have looked at threads on this issue from 12jun06
and 2jun06
and http://www.gentoo.org/doc/en/kde-split-ebuilds.xml.
By the way, this doc is good for explaining the issues,
but does not
Neil Bothwick neil at digimed.co.uk writes:
Is there an easy way to remove all of the kde packages before
migration to kde-meta?
See the thread form a couple of hours ago,
Awe, yes, Gmane runs very slow during the day (EST),
I see this recent discussion.
I think you have
Just showing a couple of tricks.
On Thursday 22 June 2006 20:15, James wrote:
Yes, That solves how to install a new kde (mono, meta, split) but
does not really address cleanzing the sytem of all the old kde kruft.
I have stuff from kde 3.2, 3.3., 3.4 on some of my older systems.
This removes
Bo Ørsted Andresen bo.andresen at zlin.dk writes:
This removes everything in kde-base that is version 3.2, 3.3 or 3.4 (and
installed of course):
# cd /var/db/pkg emerge -Cva kde-base/*-3.{2,3,4}*
Used this one. I'd rather clean it all out (KDE) and start over.
This removes everything in
On Thursday 22 June 2006 22:12, James wrote:
Ok I'll do this after emerging kde-meta completes. I hope I was not suppose
to do this before 'emerge -uavDN kde-meta'
You weren't. Blocks are only within the same slot. In fact the split packages
blocks only the monolithic package they belong
On 22/06/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote:
This will show you what packages still have cruft in /usr/kde/3.2 - 3.4:
# find /usr/kde/3.{2,3,4} | xargs equery belongs | cat
It aborts on mine:
==
# find /usr/kde/3.{2,3,4} | xargs equery belongs | cat
On Thursday 22 June 2006 23:48, Mick wrote:
It aborts on mine:
==
# find /usr/kde/3.{2,3,4} | xargs equery belongs | cat
find: /usr/kde/3.2: No such file or directory
find: /usr/kde/3.3: No such file or directory
find: /usr/kde/3.4: No such file or directory
List
On 22/06/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote:
Obviously you don't have any cruft from 3.2, 3.3 or 3.4 on that system. So all
is good.
Phew! :-))
Thanks for the nice tips! I have bookmarked it.
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
16 matches
Mail list logo
