cd x11-fm/doublecmd && make FLAVOR=qt5 install
.That's a nice trick, thank you.Next time you run into something missing, look up the port on Freshports. Then click on the "radioactive" button. That will take you to https://portsfallout.com and you can check if it failed to build. If ports fail to build they're going to be "missing" from the package repositories.
It's been having build issues: https://portsfallout.com/fallout?port=x11-fm/doublecmd$
Next time you run into something missing, look up the port on Freshports. Then click on the "radioactive" button. That will take you to https://portsfallout.com and you can check if it failed to build. If ports fail to build they're going to be "missing" from the package repositories.
Yes, that's possible. Unfortunately in that case a fallout won't be registered and you will have to dig around the actual build logs to see what happened.and if that thing is empty then an dependency failed to build.
this is often the case if you have trimmed down the options of a port and/or its dependencies.It's interesting that the GTK2 version of doublecmd is reported as failing to build as well in portsfallout.com, but I have actually built it locally from ports successfully.
% pkg search doublecmd
doublecmd-gtk2-1.1.8_1 Total Commander like file manager for the X Window System
doublecmd-qt5-1.1.8_1 Total Commander like file manager for the X Window System
doublecmd-qt6-1.1.8_1 Total Commander like file manager for the X Window System
% uname -aKU
FreeBSD mowa219-gjp4-zbook-freebsd 15.0-CURRENT FreeBSD 15.0-CURRENT main-n268772-906521f8176b GENERIC amd64 1500014 1500014
%