From owner-svn-ports-all@freebsd.org Mon May 28 20:34:56 2018 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9C15F9B97C; Mon, 28 May 2018 20:34:56 +0000 (UTC) (envelope-from yuri@freebsd.org) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5E17084069; Mon, 28 May 2018 20:34:56 +0000 (UTC) (envelope-from yuri@freebsd.org) Received: from yv.noip.me (c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id w4SKYs28072930 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 28 May 2018 13:34:55 -0700 (PDT) (envelope-from yuri@freebsd.org) X-Authentication-Warning: shell1.rawbw.com: Host c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132] claimed to be yv.noip.me Reply-To: yuri@freebsd.org Subject: Re: svn commit: r471061 - head/audio/qjackctl To: Adriaan de Groot , Sean Bruno Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org References: <201805281845.w4SIj8bO065379@repo.freebsd.org> <77503afc-b631-ac32-a87b-c8a28e0bb2ab@freebsd.org> <2187524.aIfrmmm1E6@beastie.bionicmutton.org> From: Yuri Message-ID: <98af2999-1d85-8c39-cb0f-62d4ba881dd7@freebsd.org> Date: Mon, 28 May 2018 13:34:53 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <2187524.aIfrmmm1E6@beastie.bionicmutton.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2018 20:34:57 -0000 On 05/28/18 13:10, Adriaan de Groot wrote: > Note that actively deprecating Qt4 is something that will take months, in > order to allow users to make a smooth transition -- and it is something that > needs to be discussed at length (and probably elsewhere than this list). The question here is rather: Do we need to support people who want to stay with Qt4, and not have Qt5? Because that's what is asked here. Yuri