Removing self-compiled software
Normally I use the pkgtools to install/remove packages.
But for setting up a small webserver ( only used for local development on my laptop ) i compiled apache,php and mysql. Now i want to remove these self-compiled packages completely. I thought about doing it like this: slocate [filename] > filelist Then remove the packages listet in 'filelist' Is this safe, or is there a better way to get rid of the packages ? ( I know, I should use the binarys, but I have to learn.... ;) ) |
Hi,
Try 'make uninstall' in the directory you origionally compiled in. |
Thanks for the quick reply.
The problem is, i donīt have the original directory anymore :D Letīs say, i took the php-sources, and unpacked them to /server/php-4.3.7 then i went into this directory: cd /server/php-4.3.7 Then i did: ./configure --prefix=/server/php --with-mysql=/server/mysql --with-xml --with-apache=../apache_1.3.31 --enable-track-vars make make install everything went fine, so i deleted the /server/php-4.3.7 directory ( the one with the sources ), so i just have the target-directory /server/php now, with the compiled stuff in it.... So, i canīt do make uninstall because i deleted the source directory ( ? ) How can I get rid of the complete php-installation ? ( itīs not only php, this is just an example ) |
You'll have to do it manually unfortunatly then. I used to have the same problem until i read somewhere about checkinstall and started using it. checkinstall takes the place of the "make install" command and generates a Slackware package for you and installs it. So you only have to remove the package when you don't want it anymore.
This is Checkinstall's url: http://checkinstall.izto.org/index.php Also you have some tutorial on how to create package files on http://www.linuxpackages.net (a good source of software for slack btw..) |
Thank you :)
Iīll give it a try :) |
1. download php-4.3.7 again and untar it
2. ./configure with same configure options like 1st time 3. make uninstall 4. remove this directory that's it. M. |
or even better ... for the future ...
after running ./configure and make, make slackware package, and install it with installpkg. you can remove it later with removepkg. M. |
Wouldn't it work to compile and install the exact same packages again, this time using checkinstall instead of "make install", and then remove the package with removepkg?
|
probably, but I like to make my slackware packages to have them for some future installations.
M. |
malo_umoran, checkinstall creates a package from the sources you've compiled and install it's (but also leaves the package created). So you can remove the sources and leave the package for future installations.
|
Quote:
I already downloaded checkinstall and will give it a try ( currently I rtfm :p ) And in the next couple of days I will learn how to build Slackware packages ;) You know, normally i prefer to use slackware-packages, because there is nearly nothing you canīt find for Slackware. But i have to learn how things are working ( have to know anything and everything for I can sleep at night :lol ) so I do a lot of experiments, like compiling software for the first time and wondering how to get rid of it...... Thank you for the help :cool: |
Quote:
but thanx for the info regarding checkinstall. M. |
All times are GMT -5. The time now is 01:31 AM. |