The getting_started page's Custom Location section gives the following example:
MANPATH_MAP /opt/infrastructure/clojure/bin /opt/infrastructure/clojure/man
Allowing for a different prefix that I gave the installer, the second location does not exist. I think the second location's "/man" should be "/share/man".
The long story is that, to avoid sudo, I could not follow the instructions precisely. Here's what I did to run into the problem and how I resolved it. I suppose that the resolution also applies to the sudo-related case illustrated on getting_started.
mkdir ${HOME}/opt
./linux-install-1.10.1.739.sh --prefix ${HOME}/opt/clojure
Instead of changing a man-related configuration in /etc, I added the following line to .bash_profile:
export MANPATH=":${HOME}/opt/clojure/bin:${HOME}/opt/clojure/man"
(Initial colon important to indicate that this is an addendum to system locations.) I activated the new MANPATH with source .bash_profile. But man -u clj did not yield any results.
After changing to
export MANPATH=":${HOME}/opt/clojure/bin:${HOME}/opt/clojure/share/man"
the man -u clj command worked.
The getting_started page's Custom Location section gives the following example:
Allowing for a different prefix that I gave the installer, the second location does not exist. I think the second location's "/man" should be "/share/man".
The long story is that, to avoid sudo, I could not follow the instructions precisely. Here's what I did to run into the problem and how I resolved it. I suppose that the resolution also applies to the sudo-related case illustrated on getting_started.
Instead of changing a man-related configuration in
/etc, I added the following line to.bash_profile:(Initial colon important to indicate that this is an addendum to system locations.) I activated the new MANPATH with
source .bash_profile. Butman -u cljdid not yield any results.After changing to
the
man -u cljcommand worked.