Hi, Is there a way to cleanly remove all components of self-compiled and installed programs? I like to d/l source tarballs and compile them myself so I know the binaries are optimized for my system. RPMs can be cleanly removed using YaST or 'rpm -e'. Is there a similar mechanism that keeps track of programs that were not installed as RPM? Is redirecting the output of 'make' to a text file a good idea? Regards, -- = Martijn van den Burg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Mon, 06 Sep 1999, Martijn van den Burg wrote:
Hi,
Is there a way to cleanly remove all components of self-compiled and installed programs? I like to d/l source tarballs and compile them myself so I know the binaries are optimized for my system.
RPMs can be cleanly removed using YaST or 'rpm -e'. Is there a similar mechanism that keeps track of programs that were not installed as RPM? Is redirecting the output of 'make' to a text file a good idea?
I've given this one a thought or two myself, and I've decided to just learn how to build RPMs ;). I think the ideal would be to unpack the tarball, configure it, and do an `ls -l > ~/source.tree' on the tree's root. Run make, and then `ls -l > ~/source.made' to see what changed. When you've got both files, diff the files and edit the lines that occur in both. This *should* give you at least a framework of what is going to be installed. Finally, `make install > ~/source.installed' and see what has been cp'd to where. -- -=|JP|=- (Resident GNUbie) Jon Pennington | SuSE Linux 6.2 Kansas City, Missouri, USA | Kernel 2.2.10+ uberjon@flash.net | AMD K6-350 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jon Pennington wrote:
On Mon, 06 Sep 1999, Martijn van den Burg wrote:
Hi,
Is there a way to cleanly remove all components of self-compiled and installed programs? I like to d/l source tarballs and compile them myself so I know the binaries are optimized for my system.
RPMs can be cleanly removed using YaST or 'rpm -e'. Is there a similar mechanism that keeps track of programs that were not installed as RPM? Is redirecting the output of 'make' to a text file a good idea?
I've given this one a thought or two myself, and I've decided to just learn how to build RPMs ;).
Hmm, I've been putting this off after obtaining the 400+ pages or so Maximum RPM manual. Looks like there's no escape from it now...
I think the ideal would be to unpack the tarball, configure it, and do an `ls -l > ~/source.tree' on the tree's root. Run make, and then `ls -l > ~/source.made' to see what changed. When you've got both files, diff the files and edit the lines that occur in both. This *should* give you at least a framework of what is going to be installed. Finally, `make install > ~/source.installed' and see what has been cp'd to where.
That's about what I had in mind, but prolly more thorough. Thanks.
-- -=|JP|=- (Resident GNUbie)
Jon Pennington | SuSE Linux 6.2 Kansas City, Missouri, USA | Kernel 2.2.10+ uberjon@flash.net | AMD K6-350
-- = Martijn van den Burg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Mon, 06 Sep 1999, Martijn van den Burg wrote:
Jon Pennington wrote:
I've given this one a thought or two myself, and I've decided to just learn how to build RPMs ;).
Hmm, I've been putting this off after obtaining the 400+ pages or so Maximum RPM manual. Looks like there's no escape from it now...
Actually, I've learned the most useful information by reading the document playfully called `RPM at Idle', located at: http://www.rpm.org/support/RPM-HOWTO.html It's not as in-depth as Maximum RPM (which is also available in .ps.gz format from the rpm.org site), but then again, it doesn't take two hours to print on a deskjet printer, either. :)
I think the ideal would be to unpack the tarball, configure it, and do an `ls -l > ~/source.tree' on the tree's root. Run make, and then `ls -l > ~/source.made' to see what changed. When you've got both files, diff the files and edit the lines that occur in both. This *should* give you at least a framework of what is going to be installed. Finally, `make install > ~/source.installed' and see what has been cp'd to where.
That's about what I had in mind, but prolly more thorough. Thanks.
People often complain that I'm too thorough (except in my spelling and grammar) :). The biggest problem is when you come up against a source tree that asks the user (compiler) questions. Then it sort of hangs. Otherwise, it works. -- -=|JP|=- (Resident GNUbie) Jon Pennington | SuSE Linux 6.2 Kansas City, Missouri, USA | Kernel 2.2.10+ uberjon@flash.net | AMD K6-350 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi, On Mon, Sep 06, 1999 at 08:10 +0200, Martijn van den Burg wrote:
RPMs can be cleanly removed using YaST or 'rpm -e'. Is there a similar mechanism that keeps track of programs that were not installed as RPM? Is redirecting the output of 'make' to a text file a good idea?
Try instmon: http://metalab.unc.edu/pub/Linux/system/admin/instmon-1.5.tar.gz Ciao, Stefan -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Stefan Troeger wrote:
Hi,
On Mon, Sep 06, 1999 at 08:10 +0200, Martijn van den Burg wrote:
RPMs can be cleanly removed using YaST or 'rpm -e'. Is there a similar mechanism that keeps track of programs that were not installed as RPM? Is redirecting the output of 'make' to a text file a good idea?
Try instmon:
http://metalab.unc.edu/pub/Linux/system/admin/instmon-1.5.tar.gz
Ciao, Stefan
--
Judging the description in the LSM this is exaclty what I was looking for. Thanks! -- = Martijn van den Burg -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Mon, 6 Sep 1999, Martijn van den Burg wrote: mb> Hi, mb> mb> Is there a way to cleanly remove all components of self-compiled and mb> installed programs? I like to d/l source tarballs and compile them mb> myself so I know the binaries are optimized for my system. mb> mb> RPMs can be cleanly removed using YaST or 'rpm -e'. Is there a similar mb> mechanism that keeps track of programs that were not installed as RPM? mb> Is redirecting the output of 'make' to a text file a good idea? mb> mb> Regards, mb> You can download 'instmon' from freshmeat, when launched it will keep track of what ever you install until you run instmon again. It also helps in making tgz's, rpm's, deb's and a couple others I believe. -- S.Toms - tomas@primenet.com - http://www.primenet.com/~tomas S.u.S.E. Linux v6.1+ - Kernel 2.2.11 "Well, if you can't believe what you read in a comic book, what *can* you believe?!" -- Bullwinkle J. Moose [Jay Ward] -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (4)
-
Martijn.van.den.Burg＠asml.nl -
stefan.troeger＠wirtschaft.tu-chemnitz.de -
tomas＠primenet.com -
uberjon＠flash.net