EndUserCompileAndInstall

After downloading a new package, either of a new or updated piece of software, the user will usually want to install it.

This section assumes that the user has indeed downloaded the package he wants to install. Also, it is assumed that all the necessary dependency packages have been also downloaded (see packages overview for details on how this can be achieved).

The user has two options for installing software on his machine, depending on his needs and on his expertise. He can download either a source package, containing the software's source code files and (usually) a makefile, or a binary package, containing the precompiled binary files necessary for the software's installation and execution.

The advantages of downloading the source packages, instead of downloading binary packages, are:

• The code is optimized for the user's machine, processor, architecture etc.
• Dependency problems less frequent because the code is compiled against the user's installed libraries.
• Depending on his expertise, the user can "tweak" the code and make changes for the software to fit his needs and machine.

The advantages, on the other hand, of downloading binary packages are:

• No need for user knowledge of compiling and running makefiles. Should there be problems with the compilation, most regular users will have no idea of how to solve them.
• Providing that the package was compiled for the user's specific architecture, installation should be as easy as clicking the package and choosing to install it.

Most distributions support the downloading and installation of binary packages. Some distributions rely instead on local compilation for maximum optimization of software performance. An example distribution that uses a local compilation scheme is Gentoo.

Before compiling the source code, usually the user will run a configuration script to adapt the source files for his own machine and flavor of Unix or GNU/Linux. The de-facto standard for configuration scripts is creating them using Autoconf (see "Related Tools" in the packages overview). After the configuration script has been run, compilation is taking place with the provided makefile.

When installing the software, the user is encouraged to save a backup copy of his old configuration files (if the package is an update to an already-installed package), though most developers and packagers today are aware of this issue and don't replace the old configuration files.

Users who choose to download binary packages and not compile the source on their own machines, can use any one of the package managers which work with their distribution. They can use either the package manager itself or a graphical front-end (for example Aptitude or RPMDrake).

• • Main.AssafSagi - 31 Jan 2005

{metadata}

Topics Wp2 Wp4

{metadata}