From owner-freebsd-ports@FreeBSD.ORG Sun Jun 8 20:01:03 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7E806391 for ; Sun, 8 Jun 2014 20:01:03 +0000 (UTC) Received: from um-tip2-missouri-out.um.umsystem.edu (um-tip2-missouri-out.um.umsystem.edu [198.209.49.149]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "um-tip1.um.umsystem.edu", Issuer "InCommon Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 19F2E23EB for ; Sun, 8 Jun 2014 20:01:02 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao0LAN6/lFPPoJ7U/2dsb2JhbABZgw2BK6sAAQEBAQEBBpV/gxEBgQQWdYQDAQEFcgYRAgEIGAkWDwkDAgECASAlAgQNCAEBiD7GWYUxF4VdiRaEQQSJeKNugzyCLw X-IPAS-Result: Ao0LAN6/lFPPoJ7U/2dsb2JhbABZgw2BK6sAAQEBAQEBBpV/gxEBgQQWdYQDAQEFcgYRAgEIGAkWDwkDAgECASAlAgQNCAEBiD7GWYUxF4VdiRaEQQSJeKNugzyCLw Received: from um-ncas6.um.umsystem.edu ([207.160.158.212]) by um-tip2-exch-relay.um.umsystem.edu with ESMTP; 08 Jun 2014 14:59:39 -0500 Received: from UM-MBX-T02.um.umsystem.edu ([169.254.2.161]) by UM-NCAS6.um.umsystem.edu ([207.160.158.212]) with mapi id 14.03.0181.006; Sun, 8 Jun 2014 14:59:39 -0500 From: "Montgomery-Smith, Stephen" To: "freebsd-ports@freebsd.org" Subject: Re: pkg 2 ng conversion Thread-Topic: pkg 2 ng conversion Thread-Index: AQHPg09fdXLXD9Z9AUKbJ1GWLEri15tn9YyA Date: Sun, 8 Jun 2014 19:59:38 +0000 Message-ID: <5394C0A9.5090903@missouri.edu> References: <5394B89A.4040607@paz.bz> In-Reply-To: <5394B89A.4040607@paz.bz> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 x-originating-ip: [207.160.158.205] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2014 20:01:03 -0000 On 06/08/2014 02:25 PM, 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. >=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 !! I still think you are confused. pkg manages the database that stores which ports/packages are installed on your system. Whether that particular piece of software came from building it using a port, or from downloading a binary package is immaterial. I think part of the confusion comes from the double use of the words package and/or port. When you have, say, xorg-7.7 installed on your system, do you say you have the port xorg installed, or the package xorg installed? Once it is installed it doesn't matter where it came from - port or package. For whatever reason, people tend to call it a package once it is installed, even if it came from a port. For example, when you write "pkg info" in the new system, or "pkg_info" in the old system, it reads the database to tell you the list of packages/ports installed. Now "pkg_info" and "pkg" assume a very different structure for the database. That is why, if you have installed any ports or packages using the old system, you have to run pkg2ng. It converts the database from one form to the other. And that is why if you are using FreeBSD-9 or an older system, you have to add "WITH_PKGNG=3Dyes" to make.conf, so that when more ports/packages are installed, it will update the new database and not the old. Why did the change the database structure? The old way had a separate directory for each port/package built. The new way is to use a modern relational database. So one advantage is the the new pkg database is much faster. Maybe there are other advantages too.