From owner-freebsd-ports@freebsd.org Mon Jul 24 14:13:17 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57432C7F1A0 for ; Mon, 24 Jul 2017 14:13:17 +0000 (UTC) (envelope-from rm@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 384D669A4F; Mon, 24 Jul 2017 14:13:17 +0000 (UTC) (envelope-from rm@FreeBSD.org) Received: from [127.0.0.1] (unknown [127.0.1.132]) by freefall.freebsd.org (Postfix) with ESMTP id 2AB6A6512; Mon, 24 Jul 2017 14:13:16 +0000 (UTC) (envelope-from rm@FreeBSD.org) Subject: Re: I would like to maintain and update www/luakit To: Stefan Hagen , freebsd-ports@freebsd.org References: <78a5ba6375201fc8b5a69eabb1102336@textmail.me> From: Ruslan Makhmatkhanov Message-ID: <84516e77-3662-ad85-1ae4-7782a855d01f@FreeBSD.org> Date: Mon, 24 Jul 2017 17:07:39 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <78a5ba6375201fc8b5a69eabb1102336@textmail.me> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2017 14:13:17 -0000 Stefan Hagen wrote on 07/24/2017 16:16: [...] > I can see two approches how to tackle this: > > a) leave the current www/luakit port as it is and create a new > www/luakit-gtk3 with the 2017 release. This would prevent an > automatic update for existing users. > > b) update the existing www/luakit port and add the information about > the configuration incompatibility to UPDATING. > > Any other options? > A helping hand would be appreceated. > > Best Regards, > Stefan Since there are no ports depending upon luakit, it is better to just update the existing port. Also we have two webkit-gtk3 branches: www/webkit2-gtk3 - 2.16 (stable branch, supports both apiv1 and apiv2) and www/webkit-gtk3 - 2.4 (old branch, unsupported upstream, apiv1 only) If luakit is compatible with both of them, please stick with 2.16 port. -- Regards, Ruslan T.O.S. Of Reality