Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Eh? Why do you want to mess with the binary files? If you do apt-get, it not only fetches the application but installs it too. There is nothing left to do after that (with the possible exception of a little configuration for some apps but that is nothing like installing them).
Anyway, if you do want to have a peek at the binary files, they get saved to a cache in your /var folder. That cache, by the way, can be cleaned from time to time when you don't see any reason to keep all those packages around. It's best done from the command line, not manually.
During "apt-get install", it won't tell you that where are the important files that it copy to the destination folder. That's what I'm interested to find out. Even after, "apt-get install", is there a way to trace back where those files located?
During "apt-get install", it won't tell you that where are the important files that it copy to the destination folder. That's what I'm interested to find out. Even after, "apt-get install", is there a way to trace back where those files located?
Thx.
You could use "locate sourcenav" from the command line to see where everything went. You don't need to be root to use locate.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
In addition to that:
"locate" does only work after an "updatedb". Unless you have updatedb in you cron, you have to run it manually and you have to THAT as root.
updatedb --prunepaths='/mnt'
Alternatively you can use find:
cd /
find . -name "*myprogram*"
but it takes much longer.
It is not an uncommon problem that you cannot find where apt put the binaries, and much more annoying is when apt installed binaries which do not match the package name. This happens sometime when installing packages like "network-tools" or so.
I think there is an option in apt-file to give you the same information, although like others above, I find it hard to imagine why you'd want it. You can always look at the Debian Packages website to see exactly what's included in the current version of any given package.
Most likely /usr/bin or /usr/sbin to find the files for an installed package dpkg -L package_name or if not installed and you have installed the apt-file program then ran apt-file update as root the apt-file list package_name will show you the files in the package before you install using search instead of list will find the package that contains the file you need comes in hand if compiling from source and the ./configure errors out not finding a header file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.