This sentence is mostly redundant. I'd say we can just eliminate most of it:

<command>mkfontdir</command> can be installed
as a package:</para>

With all due respect, I don't see how this is redundant as the documentation is shifting to instructions. If I remove this line, then there is a gap on what the next line is achieving. If I proceed with leaving a gap, then I am assuming the audience knows how to install a package, which I believe is what we aim not to do. Perhaps I am being overly particular in assuming that if it reads 'pkg install,' that our readers would assume that is how you install a package. I'm trying to avoid that assumption.

The redundant part is telling the reader that the software is available, and that it can be a package or port. Showing them how to install it answers those questions.

The sentence that shows the installation could be better. Some readers are going to miss that "or". Really, it is not necessary to have both. Pick the simpler way (a package) and just show that, and it eliminates a lot of explanation and uncertainty.