SEO

I recently installed KDE 3.4 successfully (I did this by putting each
required module in package.keywords with ~x86). I tried to unmerge kde
3.3.2, yet when I did

emerge -C =kde-3.3.2

I received an error that no packages were listed. Yet, kde 3.3.2 no longer
shows up if I do

emerge -Cp kde

only 3.4.

All the files are still there in /usr/kde/3.3

I did an emerge --depclean -p and two expected kde modules showed up.
ldeaccessibility and kdewebdev. I know accessibility is optional, and
webdev is being held due to a bug. But the 3.3.2 versions were unmerged
successfully.

My question is, can I safely delete the entire 3.3 tree or is there a
different unmerge command for the meta package kde?

Thx.

Peter wrote:
> My question is, can I safely delete the entire 3.3 tree or is there a
> different unmerge command for the meta package kde?
>
> Thx.

If you install kde dependent programs, such as k3b or kile, and you have not
recompile them with the kde3.4 library, deleting /usr/kde/3.3 will
certainly break library dependency of the programs.

I suggest you doing this,

1. delete /usr/kde/3.3 directory (or rename it to some thing else if you not
sure)
2. run "revdep-rebuild -p", this program will show any packages that have
broken library dependency. You can decide to recompile the package with
new library, or re-install the library itself.

Have fun,
Tom

Anocha Yimsiriwattana wrote:
> Peter wrote:
>
>>My question is, can I safely delete the entire 3.3 tree or is there a
>>different unmerge command for the meta package kde?
>>
>>Thx.
>
>
> If you install kde dependent programs, such as k3b or kile, and you have not
> recompile them with the kde3.4 library, deleting /usr/kde/3.3 will
> certainly break library dependency of the programs.
>
> I suggest you doing this,
>
> 1. delete /usr/kde/3.3 directory (or rename it to some thing else if you not
> sure)
> 2. run "revdep-rebuild -p", this program will show any packages that have
> broken library dependency. You can decide to recompile the package with
> new library, or re-install the library itself.
>
> Have fun,
> Tom
>

You can also try to use this command:

emerge -P -p `echo
kde-base/{kde{,libs,base,addons,admin,artwork,edu,games,gra phics,multimedia,network,pim,toys,utils},arts}`


Wim

On Mon, 04 Apr 2005 10:42:39 +0200, Wim Cossement wrote:

> emerge -P -p `echo
> kde-base/{kde{,libs,base,addons,admin,artwork,edu,games,gra phics,multimedia,network,pim,toys,utils},arts}`

But why would emerge -C kde not work? Why must I get rid of each component
individually? When I issued your command, every slotted program showed up
-- autoconf, docbook, gtkhtml, kernel sources, etc.

Do I need to remove each component manually? Surely, there must be a
cleaner way!

root@mars /home/peter # ls /usr/portage/kde-base//kde
ChangeLog kde-3.2.3.ebuild kde-3.4.0.ebuild
Manifest kde-3.3.1.ebuild kde-3.4.0_rc1.ebuild
files kde-3.3.2.ebuild metadata.xml
root@mars /home/peter # emerge -Cp =kde-base/kde-3.3.2

>>> These are the packages that I would unmerge:

--- Couldn't find =kde-base/kde-3.3.2 to unmerge.

>>> unmerge: No packages selected for removal.

> I recently installed KDE 3.4 successfully (I did this by putting each
> required module in package.keywords with ~x86). I tried to unmerge kde
> 3.3.2, yet when I did

qpkg -I -v -nc kde | grep "3.3.2" | xargs emerge unmerge -p

On Sun, 03 Apr 2005 21:28:41 -0400, Peter wrote:

> I recently installed KDE 3.4 successfully (I did this by putting each
> required module in package.keywords with ~x86). I tried to unmerge kde
> 3.3.2, yet when I did
>
> emerge -C =kde-3.3.2

Apparently, this had already been reported and shelved for the time being.

http://bugs.gentoo.org/show_bug.cgi?id=13133

------- Additional Comment #3 From Terje Kvernes 2003-01-10 04:48 PST -------

kde is a metapackage. it doesn't install anything on its own, all it does is
pull in dependencies. these dependecies in total become the Gentoo KDE-package.
hence, when it removes nothing, it does it's job.

if you which to uninstall what kde-base/kde installed you'll need to look at the
dependecies in that ebuild and remove them manually. portage should probably
sometime learn to understand the concept of a metapackage, so we don't have to
fake it like this, but until then, you're stuck.



Thanks for the workarounds though. There _SHOULD_ be a more user friendly
way to do this though.

Regards

Peter <peter@localhost.com> wrote:
> On Sun, 03 Apr 2005 21:28:41 -0400, Peter wrote:
> [...]
>> emerge -C =kde-3.3.2
>
> Apparently, this had already been reported and shelved for the time being.
>[...]
>
> if you which to uninstall what kde-base/kde installed
> you'll need to look at the dependecies in that ebuild and
> remove them manually.
>
>
>
> Thanks for the workarounds though. There _SHOULD_ be a more user friendly
> way to do this though.

I have not tested it, but shouldn't "emerge -D --depclean"
do the job after the above unmerge command?
If it does not, then I would consider this as a bug of --depclean,
not as a bug of the metapackage handling.

On Sun, 03 Apr 2005 21:28:41 -0400, Peter wrote:

after qpkg -I -v kde

emerging each package with =kde...3.3.2 or whichever suffix there was
allowed the entire suite to be removed.

I added a comment to the prior bug about the meta file not unmerging. It
really should. What's the point of having a one-way meta file?

Anyway, thx for the advice.

On Mon, 04 Apr 2005 10:00:16 -0400, Peter wrote:

> On Sun, 03 Apr 2005 21:28:41 -0400, Peter wrote:
>
> after qpkg -I -v kde
>
> emerging each package with =kde...3.3.2 or whichever suffix there was
> allowed the entire suite to be removed.

I meant UNmerging -- emerge -C
>

Wim Cossement enlightened us with:
> emerge -P -p `echo
> kde-base/{kde{,libs,base,addons,admin,artwork,edu,games,gra phics,multimedia,network,pim,toys,utils},arts}`

Superfluous use of backticks and echo. What's wrong with the
following?

emerge -Pp kde-base/{kde{,libs,base,addons,admin,artwork,edu,games,gra phics,multimedia,network,pim,toys,utils},arts}

I'd also replace -p with -va, btw.

Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?