svn commit: r233294 - in head: . contrib/com_err crypto/heimdal crypto/heimdal/admin crypto/heimdal/appl crypto/heimdal/appl/afsutil crypto/heimdal/appl/ftp crypto/heimdal/appl/ftp/common crypto/he...

[David Chisnall]

On 29 Mar 2012, at 04:36, Doug Barton wrote:

> All of the stuff that pkgng relies on (including the tool itself) are
> going to be in the ports collection, where they belong. We should have
> moved pkg_* there years ago, but this change is at least a step in the
> right direction.

Wait... what?  Why should pkgng be in ports (other than now, while it's under development)?  I'd like to see it used for managing some of the optional parts of the base system and probably eventually replacing freebsd-update, not have it as another bolt-on that is not part of the core system.  Not to mention the bootstrapping problem if every user who wants to use binary packages needs to use ports to build pkgng.

David