pkgng vs. portupgrade reporting ports outdated
Warren Block
wblock at wonkity.com
Sat Apr 5 04:33:23 UTC 2014
On Fri, 4 Apr 2014, sindrome wrote:
> From: Warren Block [mailto:wblock at wonkity.com]
> Sent: Friday, April 04, 2014 9:23 PM
> To: sindrome
> Cc: 'Robert Huff'; ports at freebsd.org
> Subject: RE: pkgng vs. portupgrade reporting ports outdated
>
> On Fri, 4 Apr 2014, sindrome wrote:
>
>> There is a major inconsistency with what pkg_version -v says is
>> outdated and what pkgng says.
>
> Of course. pkg_version looks at the text files in /var/db/pkg, while pkg
> looks at the database local.sqlite in that directory. The first step in
> using pkg is running pkg2ng, which imports the old information from the text
> files into the sqlite table. After that, pkg_version should not be used.
> It's getting information from an outdated database.
>
>
> So now the way to keep ports up-to-date is to execute 'pkg update' and 'pkg
> upgrade'?
>
> Are you saying I shouldn't svn update the ports tree anymore?
No, I did not say that.
By switching from the old pkg_* tools to pkg, all you have done is
changed which database is being used to track what is installed.
Nothing else needs to change.
More information about the freebsd-ports
mailing list