pkg versions don't match

[Alejandro Imass]

On Sat, Dec 20, 2014 at 3:20 PM, Adam Vande More <amvandemore at gmail.com>
wrote:

> On Sat, Dec 20, 2014 at 1:57 PM, Alejandro Imass <aimass at yabarana.com>
> wrote:
>>
>> > make that 'pkg update -f' instead .... most options are specific to the
>> > command & occur after it .... $0.02 ....
>> >
>> > --
>> >
>> >
>> Thanks guys pkg update -f worked and fixed the problem. The handbook
>> documentation pkg definitively needs work or there is some other pkg
>> hidden
>> manual besides the man page and the handbook?
>
>
> I don't know of any hidden ones, but the standard pkg manual has the
> customary 'see also' section for more in-depth information.
>
>
Yeah but something doesn't seem quite right here. The option -f "force" to
check origin versions seems a bit obscure. If -f is needed for update to
actually check remote for update then it should be more prominent.

The manual clearly states:

pkg update is used for updating the local copy of the repository catalogues
from the remote package repository databases.  Updates to catalogues are
normally downloaded only when the master copy on the remote package
repository is newer than the local copy.

So it _seems_ that update does not actually check remote pkg repository
without the use of -f

Assuming -f is needed to go and actually fetch the new versions then when a
package is not found on remote, it should be prominent in handbook page,
the main man page,  or at least hint the user to try -f when "not found".

Best,

-- 
Alejandro Imass