From owner-freebsd-ports@FreeBSD.ORG Fri Apr 3 18:48:36 2015 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 1BFD868A for ; Fri, 3 Apr 2015 18:48:36 +0000 (UTC) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D28C81B6 for ; Fri, 3 Apr 2015 18:48:35 +0000 (UTC) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 0324ABDC25; Fri, 3 Apr 2015 20:48:34 +0200 (CEST) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) by prod2.absolight.net (Postfix) with ESMTPA id B9474BDC1F; Fri, 3 Apr 2015 20:48:33 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by atuin.in.mat.cc (Postfix) with ESMTP id D8BE92EB69D2; Fri, 3 Apr 2015 20:48:32 +0200 (CEST) Date: Fri, 03 Apr 2015 20:48:32 +0200 From: Mathieu Arnold To: Mel Pilgrim , Mike Clarke , 'FreeBSD Ports' Subject: Re: Synchronising ports with package cluster Message-ID: <528E328C28D3DCE6AB98B284@atuin.in.mat.cc> In-Reply-To: <551D78BE.90109@bluerosetech.com> References: <4105121.J31zpxLvnq@curlew.lan> <551D78BE.90109@bluerosetech.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline 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: Fri, 03 Apr 2015 18:48:36 -0000 +--On 2 avril 2015 10:13:34 -0700 Mel Pilgrim wrote: | On 2015-04-01 13:42, Mike Clarke wrote: |> Where can I now obtain the revision number for the ports tree used for |> the latest package build? |> |> Although the above method has worked in the past it's a bit of a bodge. |> The ideal way would be if this information could be accessed directly |> from the relevant package repository. Would it be possible to provide |> such a facility? | | This is has been asked for many times in many forms--from SVN branching | to simply an extra bit of metadata provided by pkg itself. The usual | answer is, "we'll put this in a future version," but it remains not | implemented. Do feel free to provide a patch, adding this to, say, the repo metadata. -- Mathieu Arnold