Missing /opt/local/share/man/whatis DB

Richard L. Hamilton rlhamil at smart.net
Thu Jun 22 13:30:55 UTC 2017

Might add fc-cache to your list of programs that a port might want to run following activate/deactivate, or is that already being done as applicable?

Alll this sort of thing that could be automated seems great to me, provided it doesn't extend to that which people might reasonably want to keep in a fixed configuration despite activation/deactivation of ports; or if there were an option to disable those automatic actions which there's some slight case for wanting to do manually.

> On Jun 22, 2017, at 08:57, Rainer Müller <raimue at macports.org> wrote:
> On 2017-06-21 01:53, Stephen Baber wrote:
>> 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".
>> Presently I am letting the user know that this feature won't work for
>> them until they Terminal in and run "sudo /usr/libexec/makewhatis
>> /opt/local/share/man".
>> My question is, were there configuration consequences that MacPorts
>> needed to avoid as the reason it does not "makewhatis" itself upon
>> updating or installing ports?  All I can foresee is that the
>> additional information might change expected responses from "apropos"
>> (which would never be used in a production shell script anyway).
>> Should I not even be encouraging my users to run "makewhatis" in your
>> "/opt/local/share/man/" directory?
> This request goes in a similar direction than what we have already
> pending for info for a long time:
> https://trac.macports.org/ticket/777
> Technically, there is no hold up to add functionality to run makewhatis
> automatically, it just needs someone to do it. In the current state,
> running makewhatis manually is safe.
> Going further into the development idea for base, that would ideally be
> a generic hook interface for activate/deactivate. There are lots of
> ports that would benefit from this, all that are running utils to update
> databases after port activation.
> In addition to man and info, I can immediately think of:
>  xmlcatmgr
>  update-mime-database (shared-mime-info)
>  update-desktop-database (desktop-file-utils)
>  gtk-update-icon-cache (gtk{2,3})
>  ...
> Rainer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170622/7e401b53/attachment.sig>

More information about the macports-users mailing list