How to uninstall kaffeine which has been compiled

NoodleDoodleMan · 04-30-2006, 07:00 PM

Hi,

when i installed kaffeine i was a novice (still am!) and didnt realise the beauty of rpm's until it was too late. I installed kaffeine using the make, make install etc but now I want to remove it. (it crashes a lot, and I assume thats because of other dependencies being updated and kaffeine not) And so I want to install the new one from rpm or apt preferably.

Anyway, to my annoyance I deleted the configured data and the old tar source file. Now I cant find it on the net! version 0.7.1 I need. Is there a repository of old sources about? I cant find any so far. Once I find it I intend to configure and make uninstall, if it works... There is nothing in the readme's, forums or faq's on uninstalling sources.

Is there any other way I can remove kaffeine?

Thanks for reading!

Steve.

David the H. · 04-30-2006, 10:45 PM

I believe that, other than hunting down and deleting all the files individually, make uninstall is the only way to remove a self-compiled program. However, you can make it easier for yourself at compile time with the program 'checkinstall'. You run it instead of 'make install', and it will create a .deb or .rpm package for your program, which you can then handle in the normal way with dpkg or whatever.

There may be other programs that do something similar, but I've found this one to be very convenient. Try it out.

Anyway, that doesn't help you much here. I don't know if your idea will work, but if you want to give it a shot, remember that most open-source programs can be found on SourceForge. The source for Kaffeine 0.7.1 can be found there.
http://sourceforge.net/project/showf...ckage_id=90404

NoodleDoodleMan · 05-01-2006, 05:41 AM

Thanks for your reply, I'll use checkinstall from now on, i've just installed it.

I couldnt find the source on sourceforge when I look, must of been looking in the totally wrong place! So thanks for the link

Sadily I still cant uninstall it, the ./configure claims i dont have xine-lib installed.

*** Please install xine-lib first ***" >&5'

I install it and still the same problem, how odd? If anyone has any suggestions what to do, that'd be great!

I really dont want to hunt down the files for kaffeine, but its slowly looking like those drastic measures... where do they install them all to?

Steve

GL1800 · 05-01-2006, 05:58 AM

Here's another one of those "too little, too late" helpful thingys. I compile from source a lot, but learned from others, "good practice" to always tell configure ./configure --prefix=/usr/local. If you do that, your stuff goes into /usr/local/bin, /usr/local/lib etc. and won't interfere with the rpm versions, as they are going into /bin, or /usr/bin. This makes it much easier to clean up, as that prefix will attach to all the libraries, so that you can find them in /usr/local/lib, which will be sparsely populated and ease the removal process a lot.

NoodleDoodleMan · 05-01-2006, 06:54 AM

Thanks for the tip, i'll remember that next time. Linux, its a learning process... but i do respect and enjoy learning about it. Its just sad cos i love kaffeine, now its playing up on me

I know this is probably VERY bad practice, but can I just install the rpm over the old kaffeine made from the source? or am i going to run into big trouble doing that?

Where should I be looking for kaffeine files then?

/bin
/usr/bin

how many file should i expect to find? one kaffeine executable or loads of config files too? ugh... this is going to be a nightmare...

Thanks

GL1800 · 05-01-2006, 07:01 AM

Well, it may not be all that bad. Do a "locate" for kaffeine and libkaffeine etc. You likely will find a lot of it "clustered" together in only a few directories. After that, you'll want to TRY the rpm install and see what you get. Don't forget the rpm -ql command, showing where everything went, that may also be of help. I have dome this with no sweat, and also with a horrible experience, it just depends on what's been left over from the prior install, how your paths are picked up, etc.

David the H. · 05-01-2006, 07:06 AM

Good point about /usr/local. I'll have to start doing that myself. Still, checkinstall makes it easy enough even without that. Remember to make sure that /usr/local/bin is part of your $PATH, and /usr/local/lib is similarly in $LD_LIBRARY_PATH.

Your problem with xine-lib could be that you don't have the development files installed. Source documentation doesn't always mention that when they need libxyz, they also generally need libxyz-dev as well. I had to learn that the hard way.

So see if you have libxine-dev, or whatever it's called in FC, on your system. Of course, if it's not there, how did you manage to compile it the first time?

If you find you have to hunt the files down yourself, it shouldn't be that hard. The locate and find commands should give you most of them. If it's like most programs, the executable, or a link to it, will probably be in /usr/bin, with the bulk of the rest in a separate directory somewhere such as /usr/share. There'll probably also be a few files in /usr/lib. You may miss a file or two this way, but that shouldn't hurt your system.

ioerror · 05-01-2006, 07:20 AM

One thing you could do is to configure it again to install to some unique place (e.g. --prefix=/var/tmp/kaffeine), then make and install it. Then you have the list of files, and you can write a script to remove them, e.g.

Code:

#!/bin/sh
filelist=$(find -type f /var/tmp/kaffeine)
for f in $filelist; do
        # check that I haven't bodged something, then remove the echo (and in the dir loop below)
        echo rm $(echo $f | sed 's,/var/tmp/kaffeine,/usr/local,')
done

# now try to find unique directories that kaffeine created
dirlist=$(find -d /var/tmp/kaffeine)
for d in $dirlist; do
        # not strictly necessary since it can't remove non-empty directories anyway (e.g. /usr/local)
        if [[ -z "$(ls $d)" ]]; then
                echo rmdir $(echo $d | sed 's,/var/tmp/kaffeine,/usr/local,')
        fi
done

There are better ways to write it, but I'm feeling kinda stoopid today (hey, it's a bank holiday).

NoodleDoodleMan · 05-01-2006, 07:37 AM

Thats great, i'll give the locate a go, (i didnt know about that command, but now i do!) and just search around its hits. I cant believe i didnt know about locate, that has to be the most useful thing ever...

Thanks guys

NoodleDoodleMan · 05-01-2006, 07:45 AM

sad thing is ioerror, i cant configure, let alone make install it cos it claims i dont have xine-lib installed (even tho i do...) unless the above bypasses the xine-lib error... Thanks for the effort

ioerror · 05-01-2006, 08:05 AM

Oops, must've scrolled past that post! Does it not have an option to specify a prefix for xine-lib, like --with-xine= or something?

NoodleDoodleMan · 05-01-2006, 08:33 AM

Im a bit new, how would i find that out?? it doesnt say in the readme and this is what install file claims:

Operation Controls
==================

`configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.

`--help'
Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.

`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.

`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.

`configure' also accepts some other, not widely useful, options.

ioerror · 05-01-2006, 08:59 AM

./configure --help should list all the supported options. (The install file won't necessarily list them all).

NoodleDoodleMan · 05-01-2006, 09:16 AM

Ah, got ya, gotta love them bank holidays heh.