portmaster --check-port-dbdir doesn't understand new OPTIONS_FILE locations

[alienzoo]

Since late June the default location for new options files has changed from a simple /var/db/portname/options to /var/db/category_portname/options. When looking for obsolete port options directories portmaster doesn't understand that the new directories correspond to installed ports and offers to delete them e.g.

    ===>>> archivers_gtar does not seem to be installed
    ===>>> Delete /var/db/ports/archivers_gtar? y/n [n]
    ===>>> audio_alsa-plugins does not seem to be installed
    ===>>> Delete /var/db/ports/audio_alsa-plugins? y/n [n] 

...

make -V OPTIONS_NAME
in a port dir shows the name of the dir under /var/db/ports under which to store options. I guess portmaster will have to evaluate this for every installed port to know what are valid directories. (Note: old ports which had a directory before this framework came in still seem to stored under the port name. Not sure what happens if both dirs exist).

There may be effects beyond --check-port-dbdir :(

[bdrewery]

Fixed in 3.17.1