I was just looking at a site that offered a .gz version of a package and a RPM package. My preference is to almost always build from source with the .gz package. I feel (somewhat) like I have a better understanding what's going on. For example, a common source of problems with using mod_perl (on RedHat) is building mod_perl from source while using the Perl from RPM. The solution is to build all from source. Does anyone have any rules when to use the RPM instead of building from source? How does installing from RPM differ from building from source? Thanks, Bill Moseley mailto:moseley@hank.org -- 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 Fri, 31 Mar 2000, Bill Moseley wrote:
Does anyone have any rules when to use the RPM instead of building from source? How does installing from RPM differ from building from source?
From the rpm you type rpm -U [or whatever the right way is] and the magic program fixes everything up for you. The nice thing is it updates the datebase so when you go to upgrade to the latest SuSE version it shows the right version. Me I use the tarball if it's something important that I can't wait for. I know I could build my own rpm but it never seems worth the trouble. So my rule is rpm [if I can find SuSE rpms] for less important things. Source tarballs if it matters and I want to upgrade NOW. Not some time later when some one provides a tarball. Of course if I want to build it differently then normal then the tarball is the best way. Nick -- Nick Zentena "The Linux issue," Wladawsky-Berger explained, "is whether this is a fundamentally disruptive technology, like the microprocessor and the Internet? We're betting that it is." -- 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/
* Bill Moseley
My preference is to almost always build from source with the .gz package. I feel (somewhat) like I have a better understanding what's going on. For example, a common source of problems with using mod_perl (on RedHat) is building mod_perl from source while using the Perl from RPM. The solution is to build all from source.
Does anyone have any rules when to use the RPM instead of building from source? How does installing from RPM differ from building from source?
What I do is install all programs that I compiled in the /usr/local/ hierarchy, so that I know which ones are not rpm-based, and I know what to delete if I grow to despise the program. When you build a program, you can also do compile-time configuration which gives you a) precisely what you want and nothing more b) a smaller executable if you don't want a lot of features that don't appeal to you. (This is true for many programs like mutt, jed, slrn, etc.) When installing important software like the C library and GTK, you probably want to stick with RPM though. That way upgrading and dependencies are better achieved. "David" -- 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 (3)
-
jcm＠bigskytel.com -
moseley＠hank.org -
zentena＠hophead.dyndns.org