SlackwareThis Forum is for the discussion of Slackware Linux.
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.
The question is how was the package created. I'd bet that it was made using checkinstall?? It has a notorious behaviour in that regard. Either that or you have run manually compiled the sources and run 'make install' before creating a package using some other method. Another clue -the man-pages are not compressed, right?
tHE package is sox-12.18.1-i486-1.tgz from distro 12.0. I made
# updatedb
# slocate sox
and among the output I get
/var/man/cat1/sox.1.bz2
/var/man/cat1/soxexam.1.bz2
/var/man/cat1/soxmix.1.bz2
I also see obtain
/home/semoi/audio-uninst/sox/sox-12.18.1-i486-1.tgz-contents/usr/man/man1/sox.1.gz
/home/semoi/audio-uninst/sox/sox-12.18.1-i486-1.tgz-contents/usr/man/man1/play.1.gz
/home/semoi/audio-uninst/sox/sox-12.18.1-i486-1.tgz-contents/usr/man/man1/soxexam.1.gz
But these should be transparent to the system. Thanks.
As I'm not running 12.0 I cannot confirm this, however this is not repeated in Slackware 12.2, perhaps it is just a problem with this version of Slackware / Sox. If it is not repeated for other programs within Slackware 12.0 then it should not be a problem.
samac:
the last three paths were created by me using
explodepkg just to see what the contents of the package is. So do as if the last three don't exist. It cannot be the source of trouble. Thanks for your answer.
Usually, man-pages which are found in cat* directories are cached versions which get created when you use man to view the page. You can 'disable' the creation of cached copies by removing the dirs /var/man/cat*.
I have seen one program, though, where the sources would install man-pages in /var/man/cat.
You can cross-check the contents of the sox package by looking at the database file for it under /var/log/removed_packages.
Thanks gnashley. I now see. If they're cached, then it's a thing done by the system and not by the installer, and the uninstaller knows nothing of it. Furthermore, an installer would'nt install files in /var. Thanks very much.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.