unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: David Craven <david@craven.ch>, Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add inox.
Date: Wed, 11 Jan 2017 00:22:12 +0100	[thread overview]
Message-ID: <87o9ze8pqz.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAL1_imn==p611=2D747voSHMdLFO67PCgjcf1KQsF9A7zdYSfg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

David Craven <david@craven.ch> writes:

>> Don't get too excited yet... :)
>
> Packaging chromium is a pain in the ass... There was talk on IRC about
> inox, so I submitted my progress so far.

Tell me about it! I've been secretly maintaining a Chromium branch over
at https://github.com/mbakke/guix/commits/chromium . It's frequently
rebased.

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.

Also, Chromium 54+ have abandoned the "gyp" build system completely in
favor of the "gn" build system. With it, many build flags don't work
properly yet. See the FIXMEs in the HEAD of the above branch :-)

Anyway, great work so far, hopefully we can join efforts and get this in
somehow. I'm not happy with the current build, the 3rd party stuff
should be removed in a source snippet, and some sites tend to just
"hang" infrequently, likely from one of the patches (IPv6 probe?).

Cheers!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-01-10 23:22 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 [this message]
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
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=87o9ze8pqz.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=david@craven.ch \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).