From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PATCH] gnu: Add inox. Date: Thu, 12 Jan 2017 09:39:37 +0000 Message-ID: <87ziiwzkfa.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> References: <20170110120856.17190-1-david@craven.ch> <20170110190214.GA31184@jasmine> <87o9ze8pqz.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> <87y3yh7aj5.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cRbrO-00042I-2y for guix-devel@gnu.org; Thu, 12 Jan 2017 04:39:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cRbrK-0005Ix-Ut for guix-devel@gnu.org; Thu, 12 Jan 2017 04:39:54 -0500 Received: from aibo.runbox.com ([91.220.196.211]:57684) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cRbrK-0005Hd-Nc for guix-devel@gnu.org; Thu, 12 Jan 2017 04:39:50 -0500 In-Reply-To: <87y3yh7aj5.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> 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: Marius Bakke Cc: guix-devel@gnu.org Hi, great to see this produced something usable (although not yet shipable). Marius Bakke writes: > David Craven writes: > >>> One thing that worries me about Inox is that version 53 is very old and >>> likely contains known vulnerabilities. Do you know if they backport >>> fixes? If not, I think we should try to stick with upstream Chromium. >> >> This is due to me not having worked on it for a while. Inox are just a couple >> of patches and default configure flags, but it's still chromium. I'm not too >> concerned with inox, but *whisper* I got the impression that there where >> FSDG issues with chromium. By applying a bunch of patches and calling it >> inox instead of chromium, I think it could be considered a "good faith effort", >> and the problem avoided until someone complains. >> >> Another interesting collection of chromium patches would be: >> https://github.com/Eloston/ungoogled-chromium > > I actually picked most of the patches from ungoogled-chromium (which > includes inox and iridium), but skipped "high maintenance" ones. This > started as an attempt to package that very project, but they were > lagging too far behind upstream IMO. > > FSDG problems is the reason I haven't advertised it. At the very least, > the Google integrations should be disabled and analytics removed (but > Chromium can't currently build without either). I think if most of the > "FIXMEs" are resolved upstream, it might be eligible for a free distro. You haven't invested too much time in hoping upstream will really do this, that they really care. Last time I gave inox/chromium a try I've found https://bugs.chromium.org/p/chromium/issues/detail?id=28287 and https://bugzilla.redhat.com/show_bug.cgi?id=1270322 So either fedora really forked it (been too long since I've looked at this) or they figured out a way to improve their package. You might want to get in touch with the maintainers for chromium at fedora. > Now that the cat is out of the box, feel free to send patches somewhere > and I'll incorporate them in the branch :-) -- ♥Ⓐ ng0 -- https://www.inventati.org/patternsinthechaos/