Erik Jakobsen wrote, On 07/12/2003 11:20 PM:

...

great program to coordinate the install (and uninstall) of a tar source and the rpm database.

Hi Joe. How can checkinstall be used for uninstall. Normally I use the install/uninstall from Yast2, but I'm aware that it just remove the rpm install.

No, checkinstall does NOT uninstall, but it make uninstalling a self compiled source tarball as easy as rpm -e <package name>. Sorry if I was confusing. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 12 July 2003 12:30 pm, Erik Jakobsen wrote:

...

No, checkinstall does NOT uninstall, but it make uninstalling a self compiled source tarball as easy as rpm -e <package name>. Sorry if I was confusing.

No problem Joe. Can you please tell me a little about the uninstalling a compiled source tarball ??.

TIA

If I may. Unistalling a source/tarball is not that straight forward in some cases. One has to "rm" the specific files and directorys. Case in point: Tribes2 (a game) is installed in /usr/local/games with a symlink for the executable in /usr/bin as tribse2 (the command to create this link was ln -s /usr/game/tribes2/t2launch /usr/local/bin/tribes2). So, if it weren't for the Loki Uninstall tool/program I would have to manually remove these files and directories. The directory looks like this: /usr/local/games/tribes2> ls CardProfiles.cs README classic_files_v1.3.zip DRI-Matrox.cs README-25034 classic_v1.3.txt DRI-Radeon.cs README.network console_start.cs DRI-Rage128.cs README.tribes2d icon.bmp DRI-Voodoo3.cs README.voice icon.xpm DRI-Voodoo5.cs Radeon.cs libopenal.so.0 GeForce.cs Rage128.cs menu HighProfile.cs TNT.cs t2launch Inside_Team_Rabbit_2.txt Tribes2_Manual.pdf tribes2 Kyro.cs V2Profile.cs tribes2.dynamic LinuxCardProfiles.cs Viper.cs tribes2d LowProfile.cs Voodoo3.cs tribes2d-restart.sh Matrox.cs Voodoo5.cs tribes2d.dynamic MediumProfile.cs base uninstall Permedia3.cs classic and I have to issue the command "rm -rf /usr/local/game/tribes2" or if in the /usr/local/games directory then it's "rm -rf tribes2" and then I have to issue "rm /usr/local/bin/tribes2" (and again if in /usr/local/bin; "rm tribes2). Then if I have a symlink/shortcut/icon on my desktop I have to delete/remove that as well. This example is faily straight forward. The directories and files are conviently located. But say I wanted to remove Xine and all the files that are associated with it (like codecs and libs). Then I have to know which directories, files, and other associated stuff to remove as well - so as not to have dead/useless files cluttering things up and sucking up space. The problem herein is that some files/libs are used by other programs and others are not. So one has to know which files to safely remove/delete and which ones not to in order to get rid of the unecessary stuff for Xine but not break other apps or programs/protocols. This is the advantage of rpms overall. Though not perfect it is a time saver. Most of the time, with tarballs, it's much like I described of the tribes game. But not always. So be careful - and be good at installing and configuring things should they break. Sometime one has to do this without X or the gui. And in some cases from init S (single - meaning you have to understand mounting/read-write stuff, etc) or another init level. And the worst case scenario is reinstalling from the CD with something like update only installed packages or similar. This can be a big problem if you've added upgrades or customized you OS from the default stuff on the intallation CD's. Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/EE+yiqnGhdjCOJsRAigGAJ9uX8KybfDBCLPtGOM3FBgwqCoiBgCbBEsU dmmURDjNX2UPs6m0wluGqoE= =IpaA -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 12 July 2003 12:30, Erik Jakobsen wrote:

...

No, checkinstall does NOT uninstall, but it make uninstalling a self compiled source tarball as easy as rpm -e <package name>. Sorry if I was confusing.

No problem Joe. Can you please tell me a little about the uninstalling a compiled source tarball ??.

Curtis gave you the long version, and what would be necessary to do *if* the maker *didn't* put 'uninstall' in it. (that was meant to be a compliment Curtis...it just doesn't look like it though for some reason, but it is) So, you have a tarball, you've compiled it, installed it, run it, and don't like it. Open up a konsole, and as root, just cd to the directory of the tarball, and type 'make uninstall' (w/out the quotes). This will work only if the person who made the app and tarball put 'uninstall' in it (my experience has been about 70% *do* put uninstall in their tarball's). Once the 'make uninstall' is done, then you can rm -rf the folder. John -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/EPlVH5oDXyLKXKQRAkALAJ4pr0H4hCB2d5DfVZ/SI6/aKHUo+gCfdakp Qw6vaO2M9BrMu0V5IMdyZj4= =lRWH -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 12 July 2003 10:20 am, Erik Jakobsen wrote:

...

great program to coordinate the install (and uninstall) of a tar source and the rpm database.

Hi Joe. How can checkinstall be used for uninstall. Normally I use the install/uninstall from Yast2, but I'm aware that it just remove the rpm install.

Since checkinstall converts/makes the tarballs (.tar.gz/tar.bz2) packages into rpm's then it puts them into the rpm data base. Hence you have two options to remove/uninstall. A) rpm -e <package name> or B) YaST, find package via the search, then remove/uninistall via YaST/2. This is the whole purpose of checkinstall. Since developers make the tarballs and then the distro customize them for their specifics, e.g. RH with kde under /usr, and SuSE under /opt, etc, etc,... and then they put them into rpm form. But both of these are rpm based systems and tarball/source packages don't register in the rpm data base. The problem with this is that say you later install a program, tarball or rpm. The package will most likely do a search if a tarball for the specific dependencies it needs (like libs and others) but if you system differs from the way the developer made it (say kde and RH) then you have to give it the PATHs for the stuff like where the libs and includes are. If on the otherhand your installing a distro specific rpm and have installed some libs it needs via tarballs then those libs generally aren't registered in the rpm data base the the package (rpm) will complain that the libs/includes/whatever aren't there when you know damn well they are becuase you just installed the friggen thing (the lib/include/dependent packages). But if you installed the packages with checkinstall, then when you install the distro specific rpm then your data base know about these so you don't get complaints about packages not being there when they are. In otherwords it solves the problems inherent with tar.gz/tar.bz2 packages and rpm packages by making tarballs into rpms so the other rpms can see/know about them. Believe me, this saves a lot of hassles. Now, mind you, there are still some issues. Say you have a tar.gz package that is looking for a lib that isn't where it expects it. You still must pass the flag at ./configure like Libpath=<where ever the silly lib is>. So it's not automatic. But once you have the taball correctly configured and then the make goes with out errors or stops (at least errors that keep the package from working - some errors can be ignored), then you can pass the "checkinstall" rather than the "make install" and kill two birds with one stone - do the make install and rpm conversion all at once. Frankly it's been a real time saver and helped me avoid a lot of frustration by having to get all tarballs or all rpms. The reason this is important is because stuff llke Qamix comes only as a tarball, but you can find the dependent lib packages in rpm format. So install the rpm then the tarball (and using checkinstall you can rpm -e it later). And more inportantly is the reverse. A package like wxWindow or something else needs to be configure specifically for your distro so you must use a tarball to point it to the libs or whatever. But the only reason your installing wxWindow is because some other rpm package requires it. Now you just make one tarball via "checkinstall" and then install the rest as rpm's. Forgive the length. I just wanted to explain all in order to give a better picture. HTH. Curits. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE/EDM2iqnGhdjCOJsRArIvAJ91rTgsN/FCO+KBd17QRNVNEVhGiACdFMpS 6h2frsZFUSzBpnbOsWmt3zI= =Hw1+ -----END PGP SIGNATURE-----

looks like "/etc/checkinstallrc" in SuSE 8.2 Joe Morris (NTM) wrote:

Curtis Rey wrote, On 07/12/2003 10:28 PM:

...

Checkinstall come on the SuSE disks. It usually found at /usr/sbin/checkinstall and has it's docs at /usr/share/doc/packages/checkinstal

Don't forget /etc/checkinstall, its config file. You can have it add options to the rpm compile, like adding the i586 processor target, config the rpm command it uses, and best of all make sure the documentation it creates goes in /usr/share/doc/packages/. It is a great program to coordinate the install (and uninstall) of a tar source and the rpm database.

-- 73 de Donn Washburn __ " http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB / / __ __ __ __ __ __ __ 307 Savoy St. / /__ / / / \/ / / /_/ / \ \/ / Sugar Land, TX 77478 /_____/ /_/ /_/\__/ /_____/ /_/\_\ LL# 1.281.242.3256 a MSDOS Virus "Free Zone" OS Email: n5xwb@hal-pc.org Info: http://www.knoppix.net