From owner-freebsd-ports@FreeBSD.ORG Fri Nov 8 12:13:20 2013 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 ESMTP id B902A17E; Fri, 8 Nov 2013 12:13:20 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8F69A254D; Fri, 8 Nov 2013 12:13:19 +0000 (UTC) Received: from [192.168.0.22] (unknown [130.255.26.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 84915435C7; Fri, 8 Nov 2013 06:12:54 -0600 (CST) Message-ID: <527CD52F.7000208@marino.st> Date: Fri, 08 Nov 2013 13:12:31 +0100 From: John Marino User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: bf1783@gmail.com Subject: Re: OCaml 4? References: <830ACA3E-9233-453F-A891-2EA0F0B9F2DB@felyko.com> <527A9A9B.2040202@laposte.net> <527A9BB8.5010401@marino.st> <527AA045.7000302@laposte.net> <527AA687.9080405@marino.st> <527B2DFA.1060406@laposte.net> <527B4745.5070904@marino.st> <527BD0D6.50205@laposte.net> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: =?windows-1252?Q?Michael_Gr=FCnewald?= , Rui Paulo , FreeBSD ports , bf@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: marino@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Nov 2013 12:13:20 -0000 On 11/8/2013 12:58, Brendan Fabeny wrote: > On 11/7/13, Michael Grünewald wrote: >> John Marino wrote: >> >>> I was thinking the holdup was on your end,[…] >>> Has the whole thing stalled? 11 months to get a PR through when the >>> submitter is responsive seems excessive to me, maybe somebody else >>> should take over the PR if bf@ is too busy. >> >> It looks like it is stalled. It would actually nice if someone else >> would take care of that PR[1] but before this, I certainly need to take >> care of removing this NO_STAGE flag. It is probably unproblematic, I >> did not study this staging functionality yet. Frankly, I think it's way more important to get OCAML updated than support staging. If the PR you have is good sans staging, then I'd propose to commit that ASAP, and a new PR could be opened to add stage support. (in order words, the last of stage support should not block the maintenance of an existing port) John