File Management
Obviously software is always better installed from source. This creates binaries that are system specific. However this represents the problem of software removal. I notice some software by default will install into /usr/local then dump everything under one directory (windows style-the source install for samba is a good example). You can uses switches to put these files in the correct bin lib etc folders. So if you follow the standard(usings the systems bin/etc/sbin/man/var folders) how can you effectively remove a piece of software without having a list of all the files and paths of every app you installed. This is the only drawback to Linux I have found. Of course RPMs/dpms are away around this but lets omit pre-packaged software.
Paul Kraus
Network Administrator
PEL Supply Company
216.267.5775 Voice
216-267-6176 Fax
www.pelsupply.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 11 lines · Paul Kraus
Obviously software is always better installed from source. This creates binaries that are system specific. However this represents the problem of software removal. I notice some software by default will install into
/usr/localthen dump everything under one directory (windows style-the source install for samba is a good example). You can uses switches to put these files in the correct bin lib etc folders. So if you follow the standard(usings the systems bin/etc/sbin/man/var folders) how can you effectively remove a piece of software without having a list of all the files and paths of every app you installed. This is the only drawback to Linux I have found. Of course RPMs/dpms are away around this but lets omit pre-packaged software.
If ones installes programs from *.tar.gz archives after compiling one can simply delete the source dir and its contents, you are then left with the executable of course, when you want to "uninstall" a program reinstall the source and simply type make uninstall, in some instancies it may be nessasary to exectute a file called ./configure or even ./autogen.sh those files create a Makefile, once the Makefile is created one can then do;
make uninstall .
Mind you some older archives did not have that approch, but i guess in the modern day kernels they would not compile anyway, so we can safely say;
cd /to/source/dir
make uninstall
Quoted 7 lines
Paul Kraus
Network Administrator
PEL Supply Company
216.267.5775 Voice
216-267-6176 Fax
www.pelsupply.com
Signature · 9 lines
Regards Richard [email protected] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 4 lines · On Wednesday 18 September 2002 21:30, pa3gcu wrote:
Quoted 3 lines · Paul Kraus
Obviously software is always better installed from source. This creates binaries that are system specific. However this represents the problem of software removal.
There is a little programm, installwatch, which seems to record exactly everything which was installed in an directory, and allows to remove completly in the case you want to uninstall:
Quote: (heavy shortened ! )
--------------------------------------
TITLE: Using Installwatch as a Package Manager
LFS VERSION: Any
AUTHOR: Robert Park <[email protected]>
SYNOPSIS:
Use installwatch to keep track of what files got installed when you compiled something from source. Includes an easy method for removing those files, packaging those files up, and installing said packages.
HINT:
One big problem with LFS is that there is no package management system. This means that it is a *HUGE* pain in the butt to uninstall something, since there is no record of what got installed where, and by what program.
Requirements
------------
You'll need to download installwatch, which you can get from one of these locations:
http://asic-linux.com.mx/~izto/checkinstall/installwatch.html
http://proyectos.glo.org.mx/checkinstall/installwatch.html
If both these sites are down, try this one (but only as a last resort):
http://www.google.ca/search?hl=en&q=installwatch+izto+0.6.3&meta=
You'll also need my 'nuke' script, which is used for uninstalling software, among other things. You can get that here:
http://members.shaw.ca/feztaa/projects/nuke
4. Using Installwatch.
Now I'm going to show you how to use installwatch to create the logfiles that will be used by the nuke script.
When you are reading installation instructions for something, and you see "make install", you'll want to replace that with this:
##--CODE--##
installwatch -o /var/install/programname-version make install ##--CODE--##
5. Using Nuke.
The nuke script has many uses, the first and foremost of which is to uninstall software by analyzing installwatch logfiles.
Uninstalling software is extremely easy with the nuke script, you simply give it a logfile from /var/install, and it will remove the software from your system, and then create a logfile in /var/uninstall telling you how the uninstall went.
------------------------------------
unquote
This are hints from the project "Linux from the scratch", and I hope it will help you. Up to now, I have not used installwatch, but I am intending to do it.
Regards,
Edgar
Signature · 8 lines
-------------------------------- Dr.-Ing. Edgar Alwers Mailto: [email protected] - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 15 lines · pa3gcu wrote:
Quoted 12 lines · Paul Kraus
Obviously software is always better installed from source. This creates binaries that are system specific. However this represents the problem of software removal. I notice some software by default will install into
/usr/localthen dump everything under one directory (windows style-the source install for samba is a good example). You can uses switches to put these files in the correct bin lib etc folders. So if you follow the standard(usings the systems bin/etc/sbin/man/var folders) how can you effectively remove a piece of software without having a list of all the files and paths of every app you installed. This is the only drawback to Linux I have found. Of course RPMs/dpms are away around this but lets omit pre-packaged software.
Quoted 7 lines
If ones installes programs from *.tar.gz archives after compiling one can simply delete the source dir and its contents, you are then left with the executable of course, when you want to "uninstall" a program reinstall the source and simply type make uninstall, in some instancies it may be nessasary to exectute a file called ./configure or even ./autogen.sh those files create a
Makefile, once theMakefileis created one can then do; make uninstall .Mind you some older archives did not have that approch, but i guess in the modern day kernels they would not compile anyway, so we can safely say;
cd /to/source/dir
make uninstall
Note that there are some programs distributed as tarballs that may not have the `uninstall' rule in their Makefile. This makes them harder to remove but not impossible (<- one word that doesn't deserve a place in your vocabulary)...
Meet "checkinstall". This nifty program keeps a tab of all installed programs on your system, making it easier for you to manage them (Installing/Unistalling), by keeping a record of all write-actions performed when you do a `make install' or similar. Get it at http://proyectos.glo.mx/checkinstall/
To install the package, do:
tar xvzf checkinstall-X.Y.Z.tg
cd checkinstall-X.Y.Z
make
su (root passwd here)
make install
checkinstall
exit
To install a new package you would normally have to do
./configure
make
su (root passwd here)
make install
exit
With checkinstall installed, you have to replace the make install' step with checkinstall' so that it (checkinstall) knows what has been installed andthus makes it easier to remove. So, you would have something like:
./configure
make
su
checkinstall
exit
Hope that helps ;)
Arthur
Quoted 10 lines
Quoted 8 lines
Paul Kraus
Network Administrator
PEL Supply Company
216.267.5775 Voice
216-267-6176 Fax
www.pelsupply.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
This link does not work.
I did a google search of "Linux checkinstal" and found a home page but the app actually creates an rpm after the source is compiled.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Arthur Othieno
Sent: Thursday, September 19, 2002 9:09 AM
To: [email protected]
Cc: Paul Kraus; [email protected]
Subject: Re: File Management
Quoted 14 lines · pa3gcu wrote:
Quoted 11 lines · Paul Kraus
Obviously software is always better installed from source. This creates binaries that are system specific. However this represents the
problem of software removal. I notice some software by default will install into
/usr/localthen dump everything under one directory (windows style-the source install for samba is a good example). You can uses switches to put these files in the correct bin lib etc folders. So if you follow the standard(usings the systems bin/etc/sbin/man/var folders) how can you effectively remove a piece of software without having a list of all the files and paths of every app you installed. This is the only drawback to Linux I have found. Of
Quoted 7 lines
Quoted 3 lines
course RPMs/dpms are away around this but lets omit pre-packaged software.
If ones installes programs from *.tar.gz archives after compiling one can
simply delete the source dir and its contents, you are then left with
the
Quoted 1 line
executable of course, when you want to "uninstall" a program reinstall
the
Quoted 1 line
source and simply type make uninstall, in some instancies it may be
nessasary
Quoted 1 line
to exectute a file called ./configure or even ./autogen.sh those files
create
Quoted 7 lines
a
Makefile, once theMakefileis created one can then do; make uninstall .Mind you some older archives did not have that approch, but i guess in
the
modern day kernels they would not compile anyway, so we can safely
say;
Quoted 3 lines
cd /to/source/dir
make uninstall
Note that there are some programs distributed as tarballs that may not have the `uninstall' rule in their Makefile. This makes them harder to remove but not impossible (<- one word that doesn't deserve a place in your vocabulary)...
Meet "checkinstall". This nifty program keeps a tab of all installed programs on your system, making it easier for you to manage them (Installing/Unistalling), by keeping a record of all write-actions performed when you do a `make install' or similar. Get it at
http://proyectos.glo.mx/checkinstall/
To install the package, do:
tar xvzf checkinstall-X.Y.Z.tg
cd checkinstall-X.Y.Z
make
su (root passwd here)
make install
checkinstall
exit
To install a new package you would normally have to do
./configure
make
su (root passwd here)
make install
exit
With checkinstall installed, you have to replace the `make install' step
with `checkinstall' so that it (checkinstall) knows what has been installed andthus makes it easier to remove. So, you would have something like:
./configure
make
su
checkinstall
exit
Hope that helps ;)
Arthur
Quoted 10 lines
Quoted 8 lines
Paul Kraus
Network Administrator
PEL Supply Company
216.267.5775 Voice
216-267-6176 Fax
www.pelsupply.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs