pkgng vs. portupgrade reporting ports outdated

sindrome sindrome at gmail.com
Fri Apr 4 23:37:24 UTC 2014


	It is my understanding it is generally a bad idea to mix the old and new package systems.  (It can be done, but it's beyond my pay grade and if you're asking this I'd guess it is - at the moment - beyond yours.) "pkgng" can do almost everything the old system can, and does it better. 
  (Now if it only had a replacement for pkg_sort ....)  Each records its status quo in distinct and incompatible ways.
	When I want to know what needs updating I use:

huff>> pkg version -v -l \<

	which I can send either to a file, or to e-mail, or to a script wrapped around portmaster.

	Does this help?

Thanks Robert, but that wasn't the question.  There is a major inconsistency with what pkg_version -v says is outdated and what pkgng says.  Pkgng is reporting that everything is up-to-date and pkg_version is saying there are dozens of ports not up to date.    I'd be more than happy to use pkgng but it's clearly not seeing the same information as pkg_version.  






More information about the freebsd-ports mailing list