1. Download the desired package. 2. Open the package.a. Open a terminal and CD to the location of the package.b. Use “tar -zxvf <package .tgz>” If package name ends in .tgz.c. Use “tar -xjvf <package.tar.bz2>” for a .bz2 package.3. Read the README and any other instructions.4. Download and install any dependencies (and dependants of the dependencies).5. Run “ldconfig” to update any libraries you have just installed.

NOTE: tar.gz and .tgz are the same thing.

Installing the package (or dependencies).Open a terminal and CD to the package directory.For most packages run the following commands:

./configure (options) #configure the packagemake #compile filesmake install #copy files to the system

OR

./configure && make && make install(is this the same thing?)

./configure <options>This creates a makefile for your package detailing how the package is to be installed on your system.Options may be specified in package documentation (or elsewhere).READ THE DOCUMENTATION.In Vector 6.0 --prefix=/usr should usually be one of the options. This specifies the package is to be installed in the /usr directory.If you are updating a package already installed on the system install it to the same directory as the older version../configure --help may list the available options.

EXAMPLE: ./configure --prefix=/usr --enable-gui

“make” compiles the required files into binary files

“make install” copies the binaries into your system.

You can then clean up from the compiling process with “make clean” (in the package directory). But you will no longer be able to uninstall the package with “make uninstall”!!!Ditto if you delete your package directory!

“checkinstall” creates and installs a package for your system leaving it in thepackage directory.The checkinstall version provided is optimized for vector .Do not use another version.Use the –L switch for a .tlz package and -G for a .tgz package.The package can be uninstalled like any other with removepkgwithout damaging your system.It can be reinstalled at any time with installpkg.

Installing your package with SCONSNot all packages use the ./configure && make && make install method of installation. Some use the scons system to build and install packages.Get your package source and get it ready (see above)READ THE DOCUMENTATION.In a terminal CD to the package directory:scons configure # Configure the package. You may need options.scons # Build the scons package.scons install # Install the scons package

ORcheckinstall scons install

Other install methods:Pkgtool tukaani-pkgtools is a GUI wrapper for the make tools described above. Just follow the onscreen prompts.install scripts scons itself uses a python script for its self installation. This is run from a terminal in the package directory. READ THE DOCUMENTATION. MidnightCommander a file manager that runs in a terminal. (this could use it’s own how to)

Furthermore, you can delete all the cruft left behind AS a normal user (.o files, etc.)

Is that that same as makeclean and then deleting the source directory? Or is it a better, safer option (esp. when done as USER vs. ROOT)?

make clean rules typically remove object files, dynamically generated headers, executables, etc. I've never seen one fail, especially in the days of GNU autoconf, distutils, and others, but it could happen.

make clean does not delete the source directory (that I know of). If you build as root, revert to normal user, and then try to expunge said directory by hand, however, you will notice all those files created during the build will block your way.

The point is, you can build software just as well as normal user as you can root, and one should do things as normal user by default.