dialog4ports-0.1.6 screwed up ?
Axel Rau
Axel.Rau at Chaos1.DE
Tue Aug 28 10:59:50 UTC 2018
> Am 27.08.2018 um 13:55 schrieb Baptiste Daroussin <bapt at freebsd.org>:
>
> It could be in your environement variable also
There was no environment variable containing the string DIALOG.
Neither $HOME/.dialogrc nor /etc/dialogrc existed, but installing
the ports-mgmt/dialog4ports package manually magically resolved the issue.
Axel
---
PGP-Key:29E99DD6 ☀ computing @ chaos claudius
More information about the freebsd-ports
mailing list