Some questions have been raised about installing from source vs. installing
from a package and why I don't believe it's good to install directly from
source. I will post my reasons here.
I will first point out that nothing prevents you from building your own
package. It's not that difficult to build your own package from scratch if
need be; but usually on Debian and often on Red Hat there's a source package
available to be modified if you'd like to compile software your own way.
The reasons for installing from a package (even one you compiled yourself)
are:
- It allows you to easily know when a security patch is available, by using
one of the managers like apt, up2date, yum, etc.
- It allows you to install the exact same software binary to all your
machines. (If you were to compile from source there's a good chance for
human error to creep in and compile things differently on different
machines, leading to subtle errors which are _really_ hard to track down).
- It allows you to install software faster (this is a big consideration when
managing dozens or hundreds of machines).
- It allows you to roll back to a previous version easily, if the new one
breaks things.
- It gives you more assurance that the software will be compatible with your
already-existing software (Debian's quality control is much better than
mine would be).
- The packages often come with features compiled in by people who really
know what they're doing with the software, which you might not have
otherwise known about or been able to take advantage of.
- The packages make configuration simpler; especially in the case of dpkg,
by asking you some questions or giving you some warnings during the course
of installation.
- For those concerned about software being upgraded when they didn't want it
to be:
-- Don't blindly upgrade all your packages at once
-- With dpkg you can 'pin' packages at a certain version
-- After pinning packages at a certain version, apt will keep the
dependencies working so you don't break your software by upgrading
another library or package inadvertently
- With RPM, it records and readily displays when the package was installed.
This is valuable when figuring out when things went wrong.
- RPM has a file verification checksum feature that gives you a
first-order check to see if the files have been changed since install
time.
I've managed machines without these features, and it's truly a nightmare. If
you have one administrator, only a few machines, and enough time, you can do
it without packages. If you have several administrators, many machines, and
not enough time to do everything you'd like to, then packages are a
lifesaver.
I think I will make a FAQ item pointing out my reasons; and inviting others
to contribute their points and counterpoints.
--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/