Date: Sun, 8 Jun 2014 11:55:44 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Jim Pazarena <fports@paz.bz> Cc: freebsd-ports@freebsd.org Subject: Re: pkg 2 ng conversion Message-ID: <alpine.BSF.2.00.1406081153300.11322@wonkity.com> In-Reply-To: <5394A105.5040006@paz.bz> References: <5394A105.5040006@paz.bz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Jun 2014, Jim Pazarena wrote: > On 2014-05-28 11:30 AM, Jim Ohlstein wrote: >> Hello, >> >> On 5/28/14, 2:13 PM, Jim Pazarena wrote: >>> >>> On a new/fresh install, V10, should a person immediately place >>> "WITH_PKGNG=yes" in the make.conf ? And then is it not required >>> to run pkg2ng ? Or is it implied? It seems not, but I cannot find >>> documentation in this respect. >> >> In my experience it is unnecessary to add "WITH_PKGNG=yes" in a fresh >> FreeBSD 10 box, and it is certainly not necessary to run pkg2ng since >> there are no installed packages. >> >> The pkg_* tools are not included in FreeBSD 10 and the pkg(ng) system is >> the default. >> > > this process is a little confusing. > do I still need to run "portsnap fetch" ? If you build from ports and wish to continue using them, then yes, continue to use portsnap or svn to update the ports tree. > Or does this need to be replaced with some other ng style update? No. pkg is just a package manager. It does not replace ports, it just handles packages. Like the old package manager, binary packages can be downloaded and installed rather than ports, but the choice is yours.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1406081153300.11322>