pkgng vs. portupgrade reporting ports outdated

[sindrome]

I'm a bit confused so I figured to see if someone can help me understand the
new pkgng system better.   Before using it, I have always done a cvs update
(now svn update) to the ports tree and I would do a simple 'pkg_version
-v|grep needs' to see what ports were out-of-date and then portupgrade those
specific ports.  After I successfully built the latest versions everything
was in sync.

 

With pkgng I issue a 'pkg update' followed by a 'pkg upgrade' and it shows
me x number of ports that need to be updated.  So it updates and completes
just fine and of course it's much faster than building from source.

 

So I still keep my source, ports and docs in sync via svn update.  Here's
where the issue comes in.  After I have done the pkg upgrade and it tells me
all is up-to-date, the 'pkg_version -v |grep needs' command shows me dozens
of ports that are not up-to-date and further the versions it's saying I have
installed are not consistent with the versions that were installed through
pkgng.   If I try and portupgrade it won't upgrade the ports and just
returns me to the prompt as if there is nothing out of date.

 

Why is there such a difference here?  It seems that if I do a pkgng update /
pkg upgrade it should be consistent with the same versions that are being
reported after an 'svn update' and report back that all ports are up-to-date
no matter which command I type.  So now I can't seem to upgrade through
portupgrade to get the rest of the ports to the versions reported in the
ports tree and pkgng says I'm up-to-date.

 

It's one thing if pkgng doesn't have all the packages pre-compiled but then
it should let me portupgrade from the ports tree for those ports that aren't
available through pkgng.   I would like to get the rest of my ports
up-to-date with the ports tree like it used to work.