And ideally, anything that installs (or removes) man pages from a man page
directory should, after installing (or removing) the pages, run makewhatis, e.g.
/usr/libexec/makewhatis /opt/local/'share/man
to regenerate the index for that man page hierarchy.
That would (assuming /opt/local/share/ma
On Wed, 21 Jun 2017, Ryan Schmidt wrote:
> Other developers may have other answers as to why MacPorts doesn't do
> this, but for myself, the answer is that I'm not aware of makewhatis or
> what it does.
It's a basic Unix command; it rebuilds the manpage indices. Got to your
favourite shell wi
On Jun 20, 2017, at 18:53, Stephen Baber wrote:
> Hi MacPorts architects/maintainers,
>
> Author of JPortsUI here. I have built features into the next version
> of my application that use the "whatis" DB to describe the executable
> files installed after MacPorts completes a "port install foo".
Dear Richard,
In cases like this one please open a ticket on trac and post a link to
the mailing list, ideally macports-dev rather than the user list.
Posting a link to the mailing list might help getting more attention
from developers (but that's why you should try to use the dev list),
while op
This is being done under fresh re-install of MacPorts with the libcxx toolchain
instructions; this is the first real choke point on getting everything I had
before back, since it's needed for ImageMagick (in turn needed for other
things), git, etc.
version:1
:debug:main epoch: in tree: 0 inst
