On Wednesday, January 21, 2004, at 09:43 AM, Curtis Sloan wrote:
OK, bit of an odd question here since I know that packaging the install would eliminate the condition but obviously I was too lazy to do that. ;-)
Is there any way to accurately remove (or track down what to remove) apps compiled from source in the standard way, i.e.:
./configure make make install
For instance, would I look in the Makefile, or the ./configure log,
etc.? I guess what the question is really asking is, is there anything
in the process that keeps track of what was installed where? Or is that
why packages exist? Can I piece the information together by viewing a
few different files?
I'm not really clear on how these tarballs are created in the first place, so any links to "autoconf howto" or whatever is relevant would also be appreciated.
If you have the source directory still
you can try 'make uninstall'
If you have the source directory still and the native package format is rpm I would install checkinstall (good for the future), re-install the package using checkinstall and then rpm -e it
-- Nathanael Noblet Gnat Solutions 4604 Monterey Ave NW Calgary, AB T3B 5K4
T/F 403.288.5360 C 403.809.5368
http://www.gnat.ca/
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
