Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unix programs, in general, are not installed in a single location. It's common that a package wrote some configuration files at /etc, libraries at /lib, docs at /usr/share and executables at /usr/bin.
rpm packages have the installation directory set by the packager, the guy who built the rpm file. There is a SPEC file in this process. The paths of several files are described there. After a rpm package is installed, you can list all files that belongs to it, by "rpm -ql package-name". You can query the rpm database for what package a file belongs to, using "rpm -qf /path/to/file".
tar packages in source form, have a Makefile or a configure script that builds up the program and auxiliary files. For theses, read the README file or INSTALL file. Sometimes there is a command line option to configure/make so you can install at /usr or /usr/local.
Uninstalling a rpm package will remove all files, no matter how sparse they was installed. Packages installed with make does not have such feature. You need to remove yourself every file that belongs to a program and it can be a problem. So, prefer the rpm format when available.
1) juz wondering for tar files, since e packager set it's storage path, its there a way where we can edit DIRECTLY in e Makefile script so it goes to our desired path?
INstead of choosing only e "2 or 3" options that e packager offers? As does it really matters ?, since
/binary are e only important files.....e rest we can set it 2 other paths......so we can hv better control over while uninstallation of tar files.
Marozsas, do u have any website in particular which describe in better details what each files-sys does example;
/etc........./sbin.........../bin.......
As all my books & website that i found juz covers very briefly.
There is two ways to deal with installation paths in Makefiles. Those that use the configure script to build the Makefile, you can pass in the cmd line the installation path. This is a standard feature in configure program and should work always.
The hard way is looking at Makefile, the install section, and changing the destination path manually.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.