From mboxrd@z Thu Jan 1 00:00:00 1970 From: mike.rosset@gmail.com Subject: Re: qtwenengine anybody? Date: Mon, 16 Dec 2019 07:45:06 -0800 Message-ID: <871rt4qnp9.fsf@gmail.com> References: <87a77sqtdq.fsf@ambrevar.xyz> <87immgqryj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:36407) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1igsYX-0000hw-VZ for guix-devel@gnu.org; Mon, 16 Dec 2019 10:45:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1igsYW-0005p1-Qq for guix-devel@gnu.org; Mon, 16 Dec 2019 10:45:09 -0500 Received: from mail-pl1-x62e.google.com ([2607:f8b0:4864:20::62e]:33771) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1igsYW-0005mi-KE for guix-devel@gnu.org; Mon, 16 Dec 2019 10:45:08 -0500 Received: by mail-pl1-x62e.google.com with SMTP id c13so4647658pls.0 for ; Mon, 16 Dec 2019 07:45:08 -0800 (PST) In-Reply-To: (Hartmut Goebel's message of "Mon, 16 Dec 2019 16:22:03 +0100") 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: Hartmut Goebel Cc: Guix-devel Hartmut Goebel writes: > Hi, > > I'm glad to see there already has been some effort on this. I'll comment > on the issue. > > Am 16.12.19 um 15:13 schrieb mike.rosset@gmail.com: >> This new monolithic package stills suffers from the same issue as my >> modular qtwebengine. In that there are many in tree third party >> dependencies. It's not trivial to simply switch to guix inputs for >> these. > > IMO we should focus on a stand-alone qtwebengine package to avoid having > packages depending on a *huge* monolith. This is the most ideal situation. However the modular qtwebengine makes some assumptions which are not compatible with guix. For examples it assumes it will be installed in the same prefix as qtbase. Which is not possible with guix. The problem is also not readily obvious until you try to use qtwebengine in a library or a program. Which will causes locale and translation path issues. For the nomad browser I had had some hacks to get around this. But those hacks won't work in all cases. Because it's dependent on arg0 location. Which is not consistent when using an interpreter like guile or python or if you are using qtwebengine from a dynamic library. As of yet I have not found a proper way to resolve this. I believe the monolithic qt package at this time is the shortest route to having a sane working qtwebengine, until the locale issues can be resolved. Mike