From owner-freebsd-ports@FreeBSD.ORG Sun Nov 30 10:39:01 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA513D21 for ; Sun, 30 Nov 2014 10:39:01 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7408125A for ; Sun, 30 Nov 2014 10:39:01 +0000 (UTC) Received: from [192.168.1.239] ([212.98.32.54]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MDV5t-1Xgxvc1tUb-00Gt79 for ; Sun, 30 Nov 2014 11:38:53 +0100 Message-ID: <547AF3AE.5050803@gmx.net> Date: Sun, 30 Nov 2014 11:38:38 +0100 From: Simon Wright User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: Tracking Binary Ports/Pkgs Tree References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:JnR7mBEFeCxhNzSwq40UHHQegZtpXUiVqFVFs89ogjGdwvki2nt WlZ3+Im9o4dRmAB8HOknIe9/INQuwEhfl66JoXIbbQ5i6BosGDjt2UP6k+aYM3TttDLhWAh hvdxlOKdizsJCGSosRYacv6LIyt3eK1DCV49B4bHYYVfUP/AfIK0rTAFtu6+sIuJmDOXZcq Xo80Fcx1Bn9FnWZU0sIxw== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Nov 2014 10:39:01 -0000 Seconded. This has been an issue for me this weekend with the perl default changing to 5.18 and the gettext port split but the packages in the FreeBSD repo are still using the old default for perl and the old version for gettext whereas my local repo (with custom options) are using the new settings/ports. My preference would be to keep my local ports tree for poudriere exactly in sync with the package build port tree and to have a date/time when the repo has also been fully rebuilt so that I can run updates that will not try to pull in outdated packages. Is this position possible? My solution for this weekend has been to return to the old-faithful portupgrade and rebuild all affected ports from my current ports tree. Cheers Simon. On 30/11/2014 05:58, Reed A. Cartwright wrote: > I have been using poudriere for a while to build packages locally. I > recently reduced the package server to just the ports that I need to > have custom options. I want to rely on the freebsd pkgs as much as I > can. > > However, this has proven difficult because my ports directory is often > ahead of the one that corresponded to the latest set of binary > packages. I read where packages are build off of a snapshot of the > ports tree on every wednesday. > > Is this snapshot saved anywhere? If so, I would like to be able to > sync my local ports directory against it. If not, I would like to > request such ability. >