From: Joshua Branson <jbranso@fastmail.com>
To: guix-devel@gnu.org
Subject: Re: Firefox 52's end of life, packaging Chromium
Date: Sat, 01 Sep 2018 13:53:02 -0400 [thread overview]
Message-ID: <877ek53y0x.fsf@fastmail.com> (raw)
In-Reply-To: <878t4oylu6.fsf@aminb.org> (Amin Bandali's message of "Thu, 30 Aug 2018 10:23:45 -0400")
Amin Bandali <amin@gnu.org> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>>> 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. Would someone like
>> to investigate one of these problems?
>>
>> As has been stated multiple times in the discussion of this evolving
>> patch set, we cannot guarantee privacy, but we can make attempts to
>> remove problems as they become known. This will remain an uphill battle
>> and in future iterations of this package we should try to integrate more
>> patches provided by other groups working on removing anti-features from
>> Chromium.
>
> I highly recommend looking into ungoogled-chromium [0], which
> "modifies Google Chromium to remove Google integration and
> enhance privacy, control, and transparency". It's not exactly a
> fork, but rather a series of patches and modifications they apply
> to each Chromium release.
There is also the Brave browser
https://brave.com/
>
> In terms of documentation, they have a high-level description of
> the various components and patches [1], and build instructions
> for a few platforms and distros [2]. There was also an attempt
> to make a nix package a while ago [3], which may be helpful to
> look at.
>
> [0]: https://github.com/Eloston/ungoogled-chromium
> [1]: https://github.com/Eloston/ungoogled-chromium/blob/master/docs/design.md
> [2]: https://github.com/Eloston/ungoogled-chromium/blob/master/docs/building.md
> [3]: https://github.com/NixOS/nixpkgs/pull/30916
next prev parent reply other threads:[~2018-09-01 17:52 UTC|newest]
Thread overview: 58+ 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
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 [this message]
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-15 10:36 ` [bug#28004] " Clément Lassieur
2018-09-17 13:28 ` Chromium channel Marius Bakke
2018-09-17 14:16 ` Clément Lassieur
2018-09-17 14:16 ` [bug#28004] " Clément Lassieur
2018-09-17 18:08 ` Nils Gillmann
2018-09-17 17:57 ` Pjotr Prins
2018-09-17 17:57 ` [bug#28004] " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ek53y0x.fsf@fastmail.com \
--to=jbranso@fastmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.