From owner-freebsd-ports@FreeBSD.ORG Fri Jun 13 19:24:29 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 9BC97FF9; Fri, 13 Jun 2014 19:24:29 +0000 (UTC) Received: from yoshi.brtsvcs.net (yoshi.brtsvcs.net [IPv6:2607:f2f8:a450::66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 816332D50; Fri, 13 Jun 2014 19:24:29 +0000 (UTC) Received: from chombo.houseloki.net (unknown [IPv6:2601:7:880:bd0:21c:c0ff:fe7f:96ee]) by yoshi.brtsvcs.net (Postfix) with ESMTPSA id 9A9B9E6079; Fri, 13 Jun 2014 12:24:28 -0700 (PDT) Received: from [IPv6:2601:7:2280:38b:558a:cfd2:646d:c36a] (unknown [IPv6:2601:7:2280:38b:558a:cfd2:646d:c36a]) by chombo.houseloki.net (Postfix) with ESMTPSA id 0EE05BCA; Fri, 13 Jun 2014 12:24:26 -0700 (PDT) Message-ID: <539B4FE1.4090406@bluerosetech.com> Date: Fri, 13 Jun 2014 12:24:17 -0700 From: Darren Pilgrim Reply-To: FreeBSD Ports ML User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Baptiste Daroussin Subject: Re: Keeping my ports tree in sync with the public pkg repo References: <5399A6F1.9050109@bluerosetech.com> <20140612134202.GB2606@ivaldir.etoilebsd.net> In-Reply-To: <20140612134202.GB2606@ivaldir.etoilebsd.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Ports ML 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: Fri, 13 Jun 2014 19:24:29 -0000 On 6/12/2014 6:42 AM, Baptiste Daroussin wrote: > On Thu, Jun 12, 2014 at 06:11:13AM -0700, Darren Pilgrim wrote: >> Is there a way to determine the ports tree revision used for the current >> public pkg repo? >> > > Right now you have no way but knowing that we take a snapshot of the ports tree > at 1am UTC every wednesday and build on it I'll cron the svn update to coincide. That should make the race window narrow enough to be mostly avoided. > With pkg 1.3 we will add some metadata to the repo specifying the revision used > We also to plan to add a "ports" package so pkg install ports will install the > ports tree used to build the packages Oh nice! Exposing the revision number would be a really useful bit of info. I could easily grab that and feed it to svn.