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...

[Julien Laffaye]

On 03/29/2012 01:16 PM, David Chisnall wrote:
> 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.
Its in ports to be able to update pkgng more often. Otherwise, we would 
have to deal with old version of pkgng forever (at least as long as 
FreeBSD branches are supported). Now that it is in the ports, it is also 
a package so it knows how to upgrade itself. That means we can now 
upgrade the version of pkgng even on old FreeBSD installations. Last but 
not least, we also have fewer ABI constraints if we have to break it.
As for the boostrap problem, the bsdinstaller will install the pkgng 
package for you, so you'll have the pkg(8) command right after the first 
boot.