As we all know slackware packages can contain doinst.sh, which is executed by installpkg/upgradepkg. Many scripts used to create symbolic links or rename some files included in the package.

If I remove this package using removepkg, does the files added/modified by doinst.sh will be also removed?

Nope.

Only symlinks created by makepkg or in the exact same format as links created by makepkg will be dealt with (removed unless present as a file or identical link in another package). For example, if you have upgraded your system several times across multiple releases, you will almost certainly have some old files from glibc since some files exist as lib{,64}/incoming/filename in the package and are renamed by the doinst.sh script. Fortunately *most* packages only rebuild caches or indexes if anything, and the only leftover files will be in /etc (since they usually have a .new extension in the package itself). There used to exist tools to identify orphaned files (and I'm sure some still exist, and you could certainly script it) but it takes a long time for such commands to complete on a full installation and there will be many false positives.

3 members found this post helpful.

As T3slider says, there are tools that can do that. For example, slackroll has an orphan-search operation. It does take a lot of time to complete on the whole filesystem and false positives abound. Fortunately, you can restrict the search to a specific part of the tree. Unfortunately, /etc concentrates a lot of false positives.

3 members found this post helpful.

It's a pity that Slackware dosen't care of orphan files. I'm using my current system since version 13.something (+ patches upgrades). Lately I've been doing little cleanup and found some files from old packages.