andygoth |
07-12-2018 09:15 PM |
Quote:
Originally Posted by MadMaverick9
(Post 5878522)
If you have a clean installation you should not even have a "man.conf".
|
I wonder where it came from. I installed Slackware64-14.2 then upgraded to Slackware64-current. At what point did man.conf disappear upstream?
ap/man-1.6g-x86_64-3.txz in Slackware64-14.2 contains /etc/man.conf.new. Slackware64-current doesn't have an ap/man package, rather ap/man-pages and ap/man-db. Neither package has man.conf. Also I'll note that 14.2 has package ap/man-pages but not ap/man-db.
At some point in my upgrade, presumably when jumping from 14.2 to current, the man package was uninstalled. Apparently its old man.conf was left behind. How are such things supposed to be identified and cleaned up when removing obsolete packages?
With MANPATH unset, I ran "strace -o log man -w n clock" to get the list of files being opened by man in its quest to locate the man pages. Sure enough, it reads /etc/man_db.conf, and it doesn't even look at /etc/man.conf. The latter file might as well not even exist, so I'll happily delete it.
Today, about five hours ago, Pat released a/etc-15.0-x86_64-7.txz which removes the MANPATH lines from /etc/profile and /etc/csh.login. This fixes my problem and lets /etc/man_db.conf prevail.
However, that's not to say I don't still have a MANPATH environment variable. It's being set by /etc/profile.d/jdk.{sh,csh} as follows:
Code:
export MANPATH="${MANPATH}:${JAVA_HOME}/man"
This file isn't part of Slackware64. Rather, it came in jdk-8u172-x86_64-1_SBo. Perhaps the SlackBuilds script should be updated to patch out that one line since /usr/lib64/java/man is already present in man_db.conf. Without a MANPATH being set by /etc/profile, I end up with a MANPATH of ":/usr/lib64/java/man:/usr/lib64/java/man". (Yes, twice. Dunno why.) I'll contact Robby Workman about it, since it's his SlackBuilds script.
|