Date: Sun, 8 Jun 2014 21:44:35 +0200 From: Michael Gmelin <grembo@freebsd.org> To: Jim Pazarena <fports@paz.bz> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: pkg 2 ng conversion Message-ID: <AC059B4F-2043-4B47-A369-88A3A11E4F57@freebsd.org> 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 08 Jun 2014, at 21:25, Jim Pazarena <fports@paz.bz> wrote: >=20 >> On 2014-06-08 10:55 AM, Warren Block wrote: >> On Sun, 8 Jun 2014, Jim Pazarena wrote: >>=20 >>=20 >> 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. >=20 > 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=3Dyes" and ran > pkg2ng. But I never use packages. I always compile from ports. >=20 > So the warning appearing in each and every compile was & is very > misleading. Unless I am *still* confused !! Not really. If you build from ports that results in a binary package that is= installed using the package manager. Old pkg_* tools won't be supported aft= er September 1st, so this directly affects you, even if you build all ports y= ourself. > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AC059B4F-2043-4B47-A369-88A3A11E4F57>