From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Craven Subject: Re: texmaker, Qt and Chromium Date: Sat, 8 Oct 2016 11:12:44 +0200 Message-ID: References: <877f9kufxx.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45401) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsnga-0004w7-2I for guix-devel@gnu.org; Sat, 08 Oct 2016 05:12:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bsngW-00074L-Jm for guix-devel@gnu.org; Sat, 08 Oct 2016 05:12:51 -0400 Received: from mail-yw0-x22d.google.com ([2607:f8b0:4002:c05::22d]:34794) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsngV-00073M-Ar for guix-devel@gnu.org; Sat, 08 Oct 2016 05:12:48 -0400 Received: by mail-yw0-x22d.google.com with SMTP id w3so18027743ywg.1 for ; Sat, 08 Oct 2016 02:12:45 -0700 (PDT) In-Reply-To: <877f9kufxx.fsf@elephly.net> 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: Ricardo Wurmus Cc: guix-devel > What do you think? The alternative is to drop Texmaker and all the > other packages that depend on Chromium as distributed by Qt. Weren't you vocal on IRC about bundling and the hell it brings? Sounds like bundling is ok when it suits you... :) To be fair I've looked into packaging chromium (with the inox patchset applied) [0] and I came to the conclusion that it's impossible to debundle 100% (unless you are a full-time chromium developer working on just this and fix all the bugs that occur when using upstream packages etc. other distros only unbundle chromium to an extent, it looks like gentoo comes closest). I'm running into a python issue: EOF where object expected when importing certain modules during the build. When I execute the command that ninja ran manually it succeeds, which is weird. If I run ninja again to continue the build it fails on the next command with the same error. If you'd like to look into this... > I thought that Chromium was non-free ?? That's not quite true. The reason why chromium is sometimes considered non-free is because of some default build settings it uses. You can disable support for the chrome webstore and the hangouts extension, etc. It also shouldn't be confused with Chrome which is indeed non-free. > I'm not super familiar with Qt modules anymore, but can't we just > package the QtWebKit module? How does QtWebEngine relate to QtWebKit? QtWebKit is deprecated and no longer part of qt 5.7. [0] https://github.com/dvc94ch/guix/commit/41bbf4060e805c8607ab9dc05012c1f929f6699e