Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
02-21-2006, 11:12 PM
|
#1
|
LQ Newbie
Registered: Jan 2006
Distribution: Slackware
Posts: 24
Rep:
|
Uninstall programs?
Hi (linux newbie here)
I'm attempting to get gPhoto (and the associated library) installed. In the process, I believe I mistakenly installed an older gPhoto version with a newer library. Needless to say, it's not working as it once was. I cannot seem to reinstall.
Is there a way to unistall all gphoto and libgphoto stuff somewhat cleanly?
Thanks
V
|
|
|
02-22-2006, 01:01 AM
|
#2
|
Member
Registered: Dec 2005
Distribution: Slackware
Posts: 250
Rep:
|
Uninstall *.tgz is done either with
pkgtool --> uninstall or removepkg packagename.
If you compiled from source try make clean or make uninstall and you should have your system clean again.
Maybe it helps if you can post any error messages when trying to reinstall?
greets Isis
|
|
|
02-22-2006, 04:09 AM
|
#3
|
Senior Member
Registered: Aug 2003
Location: UK
Distribution: Slackware
Posts: 3,467
Rep: 
|
If you compiled from source use use 'make uninstall' as root
If you have done 'make clean' or 'make distclean' you will need to './configure' again, and then 'make uninstall'
Correct me if I'm wrong but 'make clean' deletes the list of files needed to be made and copied, which 'make uninstall' needs to work.
|
|
|
02-22-2006, 04:24 AM
|
#4
|
Senior Member
Registered: Jul 2004
Location: Lower Rhine region, Germany
Distribution: Slackware64 current
Posts: 1,649
Rep: 
|
Another way is to compile it again and then use checkinstall to create a package out of it and to install the program (again). After that you can use the Slackware pkgtools to uninstall it.
0) install checkinstall if haven't done this: http://slackware.it/en/pb/package.ph...l-1.5.3-i486-2
1) do "./configure" and "make" as usual
2) instead of "make install" type "checkinstall" -- this should build and install the package. If it does not install the created package automatically, do it yourself with "installpkg <name of the package>"
3) type "removepkg <name of the package>" and then install your newer version again.
The chances are good, btw, that with reinstalling the working package the libraries you mentioned will get overwritten with the working stuff. Maybe try that first.
|
|
|
02-22-2006, 08:50 AM
|
#5
|
LQ Newbie
Registered: Jan 2006
Distribution: Slackware
Posts: 24
Original Poster
Rep:
|
Perfect, and yes I did have to install from source. I used the "make uninstall" command for both gphoto2 and the library. I followed that up with an updatedb and "slocate *gphoto2*" and slocate "slocate *libphoto*". The uninstallation script worked perfect...no traces of these two programs.
I think freshly installed the proper library and program again and everything works perfect
Is there a good HOWTO or something about program installation in general? I'd like to understand a bit more about where program components go. I don't like just assuming installers put everything where it's supposed to go.
Thanks all
|
|
|
02-22-2006, 09:09 AM
|
#6
|
Senior Member
Registered: Jul 2004
Location: Lower Rhine region, Germany
Distribution: Slackware64 current
Posts: 1,649
Rep: 
|
The most applications allow to give something like "make install DESTDIR=/path/some/where". Some differ slightly and don't support this or use another syntax like "make PREFIX=/path/some/where". If you use this, you can check which files will be installed with a regular "make install". The appropriate one should be stated in the README or INSTALL file that comes with the source code.
Checkinstall is another way -- just do the "checkinstall" instead of "make install" and check the contents by unpacking it somewhere with "explodepkg".
A third way would of course be to check the Makefile, but I think that is tricky if you are not used to do this (nor am I).
|
|
|
02-22-2006, 09:52 AM
|
#7
|
LQ Newbie
Registered: Jan 2006
Distribution: Slackware
Posts: 24
Original Poster
Rep:
|
I'll deffinatly install checkinstall. Looks useful. And I too shall pass on reviewing the makefiles.
However, I'm still a bit curious as to where programs (generally) go when you define the installation location. For example, lets say I'm installing KWhatever (a KDE application) from source. In configure, I pass the --prefix /usr/local. I then make and install.
I assume the program has a lot of stuff. For example:
1) Help files (man, documentation, etc)
2) Library files
3) Executables
4) Links to the application in the "start menu".
5) Other stuff ???
In Microsoft world, you can pretty much count on applications installing the same way. Example:
1) Help files go to c:\program files\app
2) Library files go to c:\windows or the app directory
3) Exe's c:\program files\app
4) Links c:\documents and settings\all users\start menu
Is there general locations (a standard if you will) of where program components go when installed from source?
Thanks
V
|
|
|
02-22-2006, 10:01 AM
|
#8
|
Senior Member
Registered: Jul 2004
Location: Lower Rhine region, Germany
Distribution: Slackware64 current
Posts: 1,649
Rep: 
|
|
|
|
02-22-2006, 01:12 PM
|
#9
|
LQ Newbie
Registered: Jan 2006
Distribution: Slackware
Posts: 24
Original Poster
Rep:
|
Excellent links. I feel much better now that I understand how the program gets broken down.
Also, the checkinstall utility looks really good. Deffinatly a step worth taking.
Thanks greatly
|
|
|
02-22-2006, 02:42 PM
|
#10
|
Member
Registered: Apr 2004
Location: new york
Distribution: win2k,ubuntu,sw13,arch,centos5.3
Posts: 815
Rep:
|
http://www.slackersbible.org/book/ and the Slackware Linux Essentials II(Slackware Linux) by Alan Hicks and others(available in documents section at linuxpackages site as on-line version) both have good package management sections too. Good luck.
|
|
|
All times are GMT -5. The time now is 02:31 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|