Hi Everyone,

Im having problems installing uncompiled packages.

I can use apt, yum, synaptic rpm etc no probs but when it comes to compiling and installing packages from .tar then I struggle.

Heres what I do:

1. download the .tar file
2. decompress the .tar file (usually resulting in a folder containing the required files for the app and compilation)
3. as root, run the ./configure command.
4. as root, run the make command.
5. as root, run the make install command.

usually says installation successful but when i query the rpm with rpm -q packagename it says that package is not installed???

Heres what I think:

1. Does the path that i am installing the package folder from matter?
2. I think there is a simple linuxism that im not aware of that is soo simple, it is not documented (makes me feel better anyway!)

Also kinda related:

why does apt or rpm or yum never update with the latest packages? keeping up to date with vendor releases.

Many thanks,

Monkey!!!!!!!

Welcome to LQ.

Unless you install the package as an rpm the rpm database will not be updated,

rpm maintains an internal list of files of packages when you done something with the packages but if you don't use rpm utility to install a package then how can it know the package? :-) You `must' use rpm when installing a package for later use of package information with rpm -qi or rpm -qf, ...etc. Your steps are correct when installing a tarball by the way.

I think you've provided the answer to your problem in your question, in a way...
which is fine, and why rpm -q would give you results.
Don't get the terms "packages" confused here - an apt package is an 'apt package' - a precisely formatted colection of files, meta data and data for use by the package manager apt.
A tarball is not required to follow any convention, and is comprised of whatever the author deems necessary for it to perform its function. It is not part of any greater management system. Once you've done your make install, you're done! No "struggle"

(By the way, it shouldn't be necessary to run the ./configure and make as root - try not to get in the habit of su'ing flippantly.)


In order for a package manager to install the latest package, it needs to know about it. Generally, when asked to install a package, a tool such as apt will consult a local, prebuilt database of packages. It will select one from here, then go out and fetch it. To install up-to-date software, you need an up-to-date package database.
With apt, run

apt-get update

as frequently as you feel necessary.