Here’s a sample package with a rather complicated version string: in this case. So this port has been revised three times without changing the actual upstream version.
The way Free BSD versions its packages can be a bit confusing if you first see it. If a port is revised (probably to correct a mistake, add more configure options, etc), the revision number is bumped.
There are a few good reasons to lock a package – and a lot of bad ones.
Resort to locking packages when necessary but don’t trifle with it because you’re effectively cutting yourself off from updates on some packages. Probably dependencies that they share with other packages.
My previous two articles have been linked to from the Dragon Fly Digest (a very valuable resource for topics in BSD and the IT in general that I’ve been reading for years now and would like to say “thanks! Justin Sherrill pointed out that everything applies to Dragon Fly BSD as well – they have adopted Pkg quite a while ago.
And in fact you benefit from knowing your way around with Pkg in a lot of places: Free BSD obviously and a lot of Free BSD-derived operating systems like OPNsense and Hardened BSD as well as desktop-oriented offspring like Ghost BSD and True OS.