RPM is a pre-made package - you can use either a graphical tool or rpm
(CLI) to
install it.
Tarballs are source code. You can usually get away with just running
./configure && make && make install
If you need to change the install path of a package, do something like this:
./configure --prefix=/this/is/where/everything/goes
&& make && sudo make install
(or use su -c
: I'm a Zenwalker and can't really say which is preferred on RH based distros)
which will end up with a directory tree like:
/this/is/.../goes/bin
/this/is/.../goes/doc
/this/is/.../goes/share
If this is not what you want in regards to chaging the install path, feel free to be more specific, as ./configure
has the following path options:
Fine tuning of the installation
directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gccv[/usr/include]
--datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
--datadir=DIR read-only architecture-independent data [DATAROOTDIR]
--infodir=DIR info documentation [DATAROOTDIR/info]
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
--docdir=DIR documentation root [DATAROOTDIR/doc/bullet]
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
--psdir=DIR ps documentation [DOCDIR]