Date: Sun, 8 Jun 2014 18:48:11 -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.1406081842230.12915@wonkity.com> In-Reply-To: <5394B89A.4040607@paz.bz> References: <5394B89A.4040607@paz.bz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Jun 2014, Jim Pazarena wrote: > On 2014-06-08 10:55 AM, Warren Block wrote: >> On Sun, 8 Jun 2014, Jim Pazarena wrote: >> >> >> 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. > > Ahh.. therein lies the confusion. I have been compiling ports for many > years. However the compilations began nagging about converting pkg2ng. > So I investigated, and set the appropriate "WITH_PKGNG=yes" and ran > pkg2ng. But I never use packages. I always compile from ports. > > So the warning appearing in each and every compile was & is very > misleading. Unless I am *still* confused !! The package database tracks what is installed, whether it was built from a port or downloaded as a binary package. The old package database is going away, and it's time to switch. That's what pkg2ng does, reads the old installed packages database and writes the new format.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1406081842230.12915>