Bug #7583

pkg_mgr confusing versions

Added by Jeremy C. Reed over 3 years ago. Updated over 3 years ago.

Needs Patch
Package System
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


The table shows Version for the package then
the dependencies show same package name with different version.
This is confusing.

For example shows: arping 1.2.2_1 depends on arping-2.15_1

To clarify, I recommend the Version column be renamed to
"pfSense pkg Version"
and the "Package Dependencies:" be changed to "FreeBSD Package Dependencies:"
(I assume all are from FreeBSD packages.)


#1 Updated by Jim Pingle over 3 years ago

  • Status changed from New to Needs Patch

There isn't enough room in the column headers to label our internal version number "pfSense pkg version" without badly breaking the formatting.

The dependencies are not always there, some packages have no dependencies, such as purely PHP packages like System Patches, Cron, and so on. In other cases the package dependencies are completely different. If we renamed them to "FreeBSD Package Dependencies" then it would break the format if we had one of our packages depend on another one of our packages internally.

In most cases the two are set far enough apart the distinction is clear enough as-is. I don't recall seeing many (if any) gripes about the versions the way they are formatted currently. That said, if someone wants to take a shot at seeing if it can be clarified further without breaking formatting or other use cases, have at it.

Also available in: Atom PDF