Click to See Complete Forum and Search --> : Installing from tarballs. Good practices?
Although I enjoy using rpm files to install software on my machines, I do recognize that compiling source code is much more flexible since many parameters can be passed to the configure script. I'm wondering if I should be saving a copy of the Makefile when I install from source code to help prepare myself in the event that I wanted to uninstall the software or answer any odd questions about it. I've always kept a copy of the tarball on the machine, but now I'm starting to question whether that's good enough. I mean, if a copy of the Makefile isn't kept, how is an administrator supposed to know (in the future) what parameters were passed to the configure script? Also, how could an administrator uninstall the software (in a clean and efficient manner) without the Makefile?
*All these questions are based off the fact that specific parameters have been passed to ./configure
Comments?
camelrider
12-26-2000, 07:09 AM
Yup, keep 'em. Some progs even let you "make uninstall" if you have the makefile.
------------------
We'll get thisright yet!
ph34r
12-26-2000, 02:18 PM
If you are installing from source, then you may have problems with dependencies on RPMs later, since source does not get added to the rpm database of whats installed.
Source is a Good Thing - have you considered a LFS system (www.linuxfromscratch.org) or Slackware?
That is why we have /opt and /usr/local http://www.linuxnewbie.org/ubb/smile.gif
Plus one can always roll thier own rpm's though having a src.rpm makes it much easier. Next up would be a slack tgz.
------------------
Just a Tuna in the Sea of Life
This makes me curious. Can you elaborate on the comment about why you have /opt and /usr/local? I'll admit I'm still new enough to think that they're roles are almost redundant.
Just looking to develop good habits here...
Originally posted by Shad:
That is why we have /opt and /usr/local http://www.linuxnewbie.org/ubb/smile.gif
Plus one can always roll thier own rpm's though having a src.rpm makes it much easier. Next up would be a slack tgz.
Sweede
12-26-2000, 06:29 PM
/opt and /usr/local are directorys to install programs that you compile into for easy deleting of that program. using --prefix=/opt/program_name , removing the program is as easy as removing that directory.
also, dont save the Makefiles, save the config.status file. run it again if you need to reconfigure something.
Sweede,
Thanks for the tips. How do you choose between /opt and /usr/local when you are using the --prefix option? I mean, if you have both directories on the box, why would you choose one for programX and not the other?
Also, I'm curious if the config.status tip was learned out of your time spent hacking away or did you learn it from any specific book/HOWTO/etc? If it did come from a specific resource, I'd love to jump on it http://www.linuxnewbie.org/ubb/smile.gif
Thanks again,
mtf8
Originally posted by Sweede:
/opt and /usr/local are directorys to install programs that you compile into for easy deleting of that program. using --prefix=/opt/program_name , removing the program is as easy as removing that directory.
also, dont save the Makefiles, save the config.status file. run it again if you need to reconfigure something.