From owner-freebsd-ports@FreeBSD.ORG Sat Apr 5 04:12:19 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 891502F6 for ; Sat, 5 Apr 2014 04:12:19 +0000 (UTC) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 525C39F6 for ; Sat, 5 Apr 2014 04:12:19 +0000 (UTC) Received: by mail-ig0-f179.google.com with SMTP id hl10so1723784igb.12 for ; Fri, 04 Apr 2014 21:12:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=ycmSxNeC9KUw5NYqm0V0NZvhNji6eGpXtnGpQNEy/Mo=; b=t5eFz2iVmBcNde0Qku4M0UwgwPvnf/Xuos91DCMDZL32fXIzK8o1+KuDo4sGjIS/ZM 6+93VKfow4dPHQHN0dWj2vJ7in7b5yu7jaURfP4zW2hZuH9wuL5AH0zzOjz9QuW8pSBw SDqaiNX7IirPur4rsNy+eRjV+nN72ssFBzJI/c2IWS5lu1sQ50mEYM08Hqt9+9WN/9Z3 R0o02X8AhB34Q2/fCAio5IQvwfepmN6IOqh43UcVT9yQzAMnn9iPWlH2nuZrkFpj6Gs7 RyD7HpkEDwcExEie48LAzCRoyqXpEanB46OwFkW3l1ByD8wNdy/HfjDTuq4EMsvBCeyB s6aw== X-Received: by 10.50.44.115 with SMTP id d19mr7173799igm.1.1396671138709; Fri, 04 Apr 2014 21:12:18 -0700 (PDT) Received: from [172.16.0.108] (c-50-178-125-248.hsd1.il.comcast.net. [50.178.125.248]) by mx.google.com with ESMTPSA id b8sm11108619igx.3.2014.04.04.21.12.18 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 04 Apr 2014 21:12:18 -0700 (PDT) References: <533F36F0.8020803@rcn.com> <000601cf505e$d3b6bc70$7b243550$@gmail.com> <001501cf5083$8dc109d0$a9431d70$@gmail.com> Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <183E5BDE-0532-4C02-9E60-ED77F2E97A24@gmail.com> X-Mailer: iPhone Mail (11D167) From: Sindrome Subject: Re: pkgng vs. portupgrade reporting ports outdated Date: Fri, 4 Apr 2014 23:12:18 -0500 To: Warren Block Cc: "ports@freebsd.org" , Robert Huff X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Apr 2014 04:12:19 -0000 Okay so just 'pkg update' followed by 'pkg upgrade' after svn update? > On Apr 4, 2014, at 11:09 PM, Warren Block wrote: >=20 >> On Fri, 4 Apr 2014, sindrome wrote: >> From: Warren Block [mailto:wblock@wonkity.com] >> Sent: Friday, April 04, 2014 9:23 PM >> To: sindrome >> Cc: 'Robert Huff'; ports@freebsd.org >> Subject: RE: pkgng vs. portupgrade reporting ports outdated >>=20 >>> On Fri, 4 Apr 2014, sindrome wrote: >>>=20 >>> There is a major inconsistency with what pkg_version -v says is >>> outdated and what pkgng says. >>=20 >> Of course. pkg_version looks at the text files in /var/db/pkg, while pkg= >> looks at the database local.sqlite in that directory. The first step in >> using pkg is running pkg2ng, which imports the old information from the t= ext >> files into the sqlite table. After that, pkg_version should not be used.= >> It's getting information from an outdated database. >>=20 >>=20 >> So now the way to keep ports up-to-date is to execute 'pkg update' and 'p= kg >> upgrade'? >>=20 >> Are you saying I shouldn't svn update the ports tree anymore? >=20 > No, I did not say that. >=20 > By switching from the old pkg_* tools to pkg, all you have done is changed= which database is being used to track what is installed. Nothing else needs= to change.