unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@libertad.pw>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add inox.
Date: Thu, 12 Jan 2017 09:39:37 +0000	[thread overview]
Message-ID: <87ziiwzkfa.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87y3yh7aj5.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>

Hi,

great to see this produced something usable (although not yet
shipable).

Marius Bakke <mbakke@fastmail.com> writes:

> David Craven <david@craven.ch> 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/

  parent reply	other threads:[~2017-01-12  9:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 12:08 [PATCH] gnu: Add inox David Craven
2017-01-10 19:02 ` Leo Famulari
2017-01-10 19:08   ` David Craven
2017-01-10 19:12     ` David Craven
2017-01-10 23:22       ` Marius Bakke
2017-01-11  8:56         ` David Craven
2017-01-11 17:48           ` Marius Bakke
2017-01-11 19:56             ` David Craven
2017-01-11 23:53               ` David Craven
2017-01-12 17:22               ` Marius Bakke
2017-01-12 18:21                 ` David Craven
2017-01-12 18:42                   ` Marius Bakke
2017-01-26 19:36                     ` David Craven
2017-01-12  9:39             ` ng0 [this message]
2017-01-10 19:16     ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ziiwzkfa.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
    --to=ng0@libertad.pw \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).