From owner-freebsd-questions@FreeBSD.ORG Wed Apr 9 15:15:41 2014 Return-Path: Delivered-To: freebsd-questions@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 72327E3 for ; Wed, 9 Apr 2014 15:15:41 +0000 (UTC) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::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 38E50151E for ; Wed, 9 Apr 2014 15:15:41 +0000 (UTC) Received: by mail-ob0-f179.google.com with SMTP id va2so2830305obc.38 for ; Wed, 09 Apr 2014 08:15:39 -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=8lYHEm9QxmC+xubw7tzm6x+t1c5oGLyNiNw4T5FHtKs=; b=d82nhmxZksalGove44Nsle5m/LJ4Qifya4gqOGJorRLfvlGrsYc3GvUKmfwdDaOGkv OBBrBo3wdFdcb94JxySElq1U2bBmVouf9Yhnfx9oWa19HFyvwSFJtcBUST1ochvWiLrk vQRvAGQEU70eRHqxK4A/ySHkfJYiYtN5YFjZqOd94kGZDChilLiWSSnhPXNwSbFCWwXL MjtiiUe1FncJHXGp2imp/Tivw7Ge8MJIxMOuDwRAz9Tk0eJSvYNVAwmRZ/ziSmKsbBm1 bTABgbzqoKwfM6Msx2FPuI6qMVemUK32qbroo/oZn/Ztar+wwym0wNE+639VnvjtPW9p +j0A== X-Received: by 10.182.219.167 with SMTP id pp7mr538635obc.85.1397056539589; Wed, 09 Apr 2014 08:15:39 -0700 (PDT) Received: from [192.168.1.64] (pool-71-170-112-253.dllstx.fios.verizon.net. [71.170.112.253]) by mx.google.com with ESMTPSA id np9sm1313705obc.12.2014.04.09.08.15.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Apr 2014 08:15:38 -0700 (PDT) References: <534520DE.5060005@relst.nl> Mime-Version: 1.0 (1.0) In-Reply-To: <534520DE.5060005@relst.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <81531653-3582-4101-8F27-F783316D0B54@gmail.com> X-Mailer: iPad Mail (11D167) From: Matthew Pherigo Subject: Re: FreeBSD Handbook, upgrading ports incorrect with 10.0-RELEASE? Date: Wed, 9 Apr 2014 10:15:38 -0500 To: Remy van Elst Cc: "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2014 15:15:41 -0000 > On Apr 9, 2014, at 5:28 AM, Remy van Elst wrote: >=20 > As I just tried, replacing pkg_version -l "<" with pkg version -l "<" (not= e the underscore) gives the same result and allows me to recompile/update th= e ports that are outdated. >=20 > Maybe this can be added to the handbook? As in, for non-pkgng do this, for= pkgng do this. I find my level of knowledge on FreeBSD not enough to submit= a patch myself, therefore the mailing list seems good. Hi Remy, I'm not sure this is really the correct way to do this in the first place. Are you using binary packages, or are you just installing things from the po= rts tree? If you're just using binary packages, the best method is "pkg upgrade". If y= ou are using ports, the method most people would use would be "portmaster -a= D" (meaning "install all upgrades and clean up all downloaded files afterwor= ds"), though I don't think portmaster is installed by default. Maybe I'm missing something, but I just don't see why you would use this "pk= g_version" method as opposed to the proper functions for upgrading. To me, i= t sounds like that method may have been originally used before these functio= ns became available. --Matt=