yeah, cause i don't know what i'm talking about admin'ing 4 production servers.
Good thing your employer doesn't understand how much time you're wasting.
1st you say that compiling from source is not best? then you talk about building from source if done properly
Re-read the sentance, it makes perfect sense. If it still doesnt, try
this.
let us refer to the pizza analogy... using an rpm is like getting a pizza kit...
Not quite. Using an rpm is like buying a pizza from the local pizza-place. Made by the guy who's been in the business for most of his life. Made by the guy who feeds his children based on the sales of his pizza.
Building from source is like buying a pizza kit. Pretty much everything is proveded for you, its just up to you to stitch it all together and come up with the finished product. You're honestly telling me damn near any of us could make a better boboli than the local guy's pizza?
Plus we're just talking about installing. When custom-source-build installations really kick you in the ass is un-installing and upgrading (with the exception of ports-based systems). We all know the tricks, sometimes you can do a make-uninstall, sometimes you can diff an updatedb before and after, but all of it is a waste of time compared to a package manager that will remove all applicable files, make a backup copy of all config files, and install all the new binaries in a single command.
Building from source is almost always a waste of time. You waste time downloading all the patches and modules you want, you waste time patching the source tree, you waste time compiling. For something like apache+php+mysql to build it all from source would take at least an hour (assuming a respectible broadband download and a relativly new/fast machine to compile on). In that same hour I can spend about 10min installing the rpm's on a test machine, 20min running httperf on it, check the error log for any segfaults, and another 5 to scp it to the production machine and install it. Based on time alone any IT department that allows linux into their datacenter should force their dimmer server admins to stick to the distro's package management system. Not to mention reliability. The people at RedHat & SuSE have hundreds of test servers, thousands of example-configs, and full-time dedicated staff to running that package through every possible scenario making sure it doesnt conflict/crash/segfault/etc. Even debian, with no dedicated staff or hardware, manages to test the bejezus out of its packages through a slower release cycle and a gigantic install base.
There's nothing 37337 about running ./configure && make && make install
(the exception to some of my compiling comments are ports-based systems.)
bart