[MacPorts] #71984: Issues with 'MANPATH', and [the lack of a macport for] 'whereis'
MacPorts
noreply at macports.org
Sat Feb 1 01:44:08 UTC 2025
#71984: Issues with 'MANPATH', and [the lack of a macport for] 'whereis'
--------------------------+--------------------
Reporter: seamusdemora | Owner: (none)
Type: request | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port:
--------------------------+--------------------
I read the documentation in "The Guide" under `para 2.5.1, Optional:
MANPATH variable`. I then checked my system (via `echo $MANPATH`), and
learned that MANPATH remains `unset`. Can someone explain why it wasn't
set - or rather the reasoning behind the default condition?
WRT the 2nd issue (reached by pondering the 1st issue):
{{{
% whereis rsync # NOTE 1
rsync: /usr/bin/rsync /opt/local/share/man/man1/rsync.1.gz
}}}
Here's what the command above says:
''the `rsync` you will run is the Apple version (/usr/bin/rsync), but the
manual you will get is from MacPorts.''
As it turns out, this is partly UNTRUE (the part about where the binary is
located). FWIW, here's [https://superuser.com/a/1833522/907399 a post]
that may still explain it.
Why can't there be a macport for `whereis`?
--
Ticket URL: <https://trac.macports.org/ticket/71984>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list