From owner-freebsd-questions@FreeBSD.ORG Wed Sep 24 19:10:58 2014 Return-Path: Delivered-To: freebsd-questions@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 28E8B4B4 for ; Wed, 24 Sep 2014 19:10:58 +0000 (UTC) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E6FC8CDA for ; Wed, 24 Sep 2014 19:10:57 +0000 (UTC) Received: from kabini1.local (rbn1-216-180-19-35.adsl.hiwaay.net [216.180.19.35]) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id s8OJAtxP031249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 24 Sep 2014 14:10:55 -0500 Message-ID: <542318B6.3000206@hiwaay.net> Date: Wed, 24 Sep 2014 14:17:10 -0500 From: "William A. Mahaffey III" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: pkg must be version 1.3.8 or greater References: <5422B1C5.1030400@hiwaay.net> <44vbocyjcp.fsf@be-well.ilk.org> In-Reply-To: <44vbocyjcp.fsf@be-well.ilk.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Sep 2014 19:10:58 -0000 On 09/24/14 13:16, Lowell Gilbert wrote: > "William A. Mahaffey III" writes: > >> The portsnap messes with pkg's logic about what needs upgrading & what >> doesn't, there have been other posts on this topic over the last >> several weeks (notably from me) > Aside from the fact that the package repositories lag behind the ports > tree (which is unavoidable until someone manages to procure some > infinitely fast computers on which the build clusters can run), I can't > tell which posts are in question. > >> .... Ports & Pkg's are usually updated >> by the maintainers about weekly, ports often/usually on Wednesday, >> Pkg's on Saturday. > Maintainers make changes whenever they want (except when a release is > being prepared, in which case major changes are discouraged, a process > often referred to as a "slush"). Packages are being built continuously, > and a full set seems to be taking three or four days at the moment. > >> My experience is that if you wait until Saturday, >> your 'pkg-upgrade' will work as desired & you will be off to the >> races. > If your particular ports updates happen to be getting committed > mid-week, that sounds about right. The build cluster will be fairly > certain to have built them into packages three days later. But, again, > there's no actual schedule. > >> Alternatively, you can 'pkg install -yf ....' your pkg & move >> on immediately .... In general, for me, you should do any pkg-upgrades >> *before* you mess w/ ports. > I would expect that to be less annoying than the other way around. Agreed :-) .... That was kinda the point of the whole post. I do think I am pretty close to right on my days of (most) commits, I got that from an earlier (a few weeks) post on this very topic .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.