From owner-svn-ports-all@freebsd.org Mon May 28 19:11:03 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 4013FF78826; Mon, 28 May 2018 19:11:03 +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 D28637C5A3; Mon, 28 May 2018 19:11:02 +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 w4SJB1o6065032 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 28 May 2018 12:11:02 -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: Sean Bruno , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org References: <201805281845.w4SIj8bO065379@repo.freebsd.org> <985846ee-dce7-d8f1-2813-0a28bc36217e@freebsd.org> <5dddd567-3439-caa3-56d0-665a40bdbf35@freebsd.org> From: Yuri Message-ID: <77503afc-b631-ac32-a87b-c8a28e0bb2ab@freebsd.org> Date: Mon, 28 May 2018 12:11:00 -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: <5dddd567-3439-caa3-56d0-665a40bdbf35@freebsd.org> Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.26 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 19:11:03 -0000 On 05/28/18 12:02, Sean Bruno wrote: > The problem I am describing is that*if* I am using applications that > are QT4 only, this change now forces me too build QT5 to get this one > port built. > > Maybe its better to leave QT4 in place but make QT5 the default? I made such changes before (deprecate Qt4) elsewhere and nobody complained. It's like if some package is updated from mypkg-4.0 to mypkg-5.0, the port changes to mypkg-5.0, and the users have to update. The ports system doesn't provide a way to stay with mypkg-4.0. Why Qt should be different? It has to deprecate Qt4 at some point. Qt4 hasn't been shown to provide any benefit, generally. If some app doesn't support Qt4, you should complain to that app, IMO. Your situation sounds like a fringe case that most users don't care about. Yuri