From: Ricardo Wurmus <rekado@elephly.net>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: guix-devel@gnu.org
Subject: Re: Firefox 52's end of life, packaging Chromium
Date: Thu, 30 Aug 2018 14:11:21 +0200 [thread overview]
Message-ID: <87lg8o9hqu.fsf@elephly.net> (raw)
In-Reply-To: <8736uw2q0g.fsf@lassieur.org>
Hi Clément,
>>> So the question is: can we push the Chromium package? I've read it's
>>> almost ready[2].
>>
>> The TODO list for convenience:
>>
>> --8<---------------cut here---------------start------------->8---
>> * There is still some data transmitted when starting the browser for the
>> first time. It seems related to the "domain_reliability" component.
>> * Remove remaining "Web Store" links. Currently I've only found it in
>> settings, under "accessibility" and "fonts".
>> * Opening settings transmits a bunch of data, the next version will
>> include the 'disable-translation-lang-fetch' patch from Inox.
>> * PDFium is built, but does not seem to work (the 'install' phase
>> probably needs tweaking). Might just disable it instead.
>> --8<---------------cut here---------------end--------------->8---
>>
>> It would be *very* nice if the first and third items could be solved
>> before merging, but I don’t consider them blockers.
>
> It's not clear to me :-) Does it mean we can merge?
I’ll leave that up to Marius, because he is much more familiar with the
patch than I am.
I would not object to merging it, but I’d like to see these TODOs as
separate bug reports, with the first and third items at a higher
severity than “normal”.
--
Ricardo
next prev parent reply other threads:[~2018-08-30 12:22 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 9:03 Firefox 52's end of life, packaging Chromium Clément Lassieur
2018-08-29 15:24 ` Pierre Neidhardt
2018-08-29 16:14 ` Christopher Lemmer Webber
2018-08-29 18:16 ` Leo Famulari
2018-08-29 21:25 ` Amirouche Boubekki
2018-08-29 22:35 ` Clément Lassieur
2018-08-29 23:26 ` Amirouche Boubekki
2018-08-30 7:43 ` Clément Lassieur
2018-08-30 1:12 ` Mike Gerwitz
2018-08-30 5:14 ` Clément Lassieur
2018-08-30 9:55 ` Ludovic Courtès
2018-08-30 10:04 ` Nils Gillmann
2018-08-30 11:01 ` Clément Lassieur
2018-08-30 12:09 ` Ludovic Courtès
2018-08-30 13:30 ` Nils Gillmann
2018-08-30 11:00 ` Clément Lassieur
2018-08-30 16:35 ` Mike Gerwitz
2018-08-30 9:07 ` Nils Gillmann
2018-08-30 9:20 ` Nils Gillmann
2018-08-30 16:38 ` Mike Gerwitz
2018-08-30 8:41 ` Ricardo Wurmus
2018-08-30 8:54 ` Clément Lassieur
2018-08-30 12:11 ` Ricardo Wurmus [this message]
2018-08-30 14:23 ` Amin Bandali
2018-09-01 14:08 ` Ludovic Courtès
2018-09-01 17:31 ` Nils Gillmann
2018-09-01 20:28 ` Amin Bandali
2018-09-02 13:54 ` Marius Bakke
2018-09-02 16:21 ` Mark H Weaver
2018-09-01 17:53 ` Joshua Branson
2018-09-01 23:18 ` Nils Gillmann
2018-09-03 20:57 ` Joshua Branson
2018-09-04 8:13 ` Nils Gillmann
2018-09-02 5:33 ` Mark H Weaver
2018-09-02 6:35 ` Mark H Weaver
2018-09-02 8:13 ` Mark H Weaver
2018-09-02 10:21 ` Ricardo Wurmus
2018-09-02 13:29 ` Marius Bakke
2018-09-02 16:48 ` Ricardo Wurmus
2018-09-04 21:44 ` Ludovic Courtès
2018-09-02 6:52 ` Leo Famulari
2018-08-30 9:57 ` Ludovic Courtès
2018-09-07 9:29 ` Clément Lassieur
2018-09-15 10:36 ` Clément Lassieur
2018-09-17 13:28 ` Chromium channel Marius Bakke
2018-09-17 14:16 ` Clément Lassieur
2018-09-17 18:08 ` Nils Gillmann
2018-09-17 17:57 ` Pjotr Prins
2018-09-22 12:44 ` Ludovic Courtès
[not found] <mailman.598.1535619290.1280.guix-devel@gnu.org>
2018-08-30 23:38 ` Firefox 52's end of life, packaging Chromium Benjamin Slade
2018-08-31 16:57 ` Hartmut Goebel
2018-09-01 14:13 ` Ludovic Courtès
2018-09-01 18:44 ` Pjotr Prins
2018-09-02 4:57 ` Mike Gerwitz
2018-09-05 20:57 ` Christopher Lemmer Webber
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=87lg8o9hqu.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=clement@lassieur.org \
--cc=guix-devel@gnu.org \
/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).