From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 24/24] gnu: qt: Update qt to 5.7.0. Date: Sat, 20 Aug 2016 17:59:57 -0400 Message-ID: <20160820215957.GA6502@jasmine> References: <20160816183938.22794-1-david@craven.ch> <20160816183938.22794-24-david@craven.ch> <87bn0pvbys.fsf@netris.org> <874m6gha9c.fsf@netris.org> <87bn0nuvfo.fsf@netris.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57852) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bbEJN-0006ow-UF for guix-devel@gnu.org; Sat, 20 Aug 2016 18:00:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bbEJK-0007kx-QR for guix-devel@gnu.org; Sat, 20 Aug 2016 18:00:17 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:55553) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bbEJH-0007ch-S2 for guix-devel@gnu.org; Sat, 20 Aug 2016 18:00:14 -0400 Content-Disposition: inline In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: David Craven Cc: guix-devel On Sat, Aug 20, 2016 at 09:50:51PM +0200, David Craven wrote: > I fixed all regression except vlc and avidemux (locally). I'll have to > do some more debugging tomorrow. Forcing --std=gnu++11 worked in all > other cases. With the release of vlc 3 eminent, would it be acceptable > to use qt-4 with vlc 2.2.4 (if I don't manage to fix it)? That's what > arch linux is doing currently - and forcing --std=gnu++98, since > they're on gcc6. My interpretation of the Qt security policy is that qt-4 is unsupported. "What Version of Qt are Supported? Fixes are only guaranteed to be provided for: The latest released version. The preceding minor version. Fixes for earlier versions (such as 4.8, 5.0, etc.) may be provided, but the qt-project makes no commitment to do so. Other groups such as Digia may choose to make such fixes available, but that is outside the scope of the qt-project." source: https://wiki.qt.io/Qt_project_security_policy