unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: Firefox 52's end of life, packaging Chromium
Date: Sun, 02 Sep 2018 12:21:00 -0400	[thread overview]
Message-ID: <87pnxvyioj.fsf@netris.org> (raw)
In-Reply-To: <87lg8kj97l.fsf@fastmail.com> (Marius Bakke's message of "Sun, 02 Sep 2018 15:54:38 +0200")

Marius Bakke <mbakke@fastmail.com> writes:

> Amin Bandali <amin@gnu.org> writes:
>
>> As for the "lagging too far behind upstream" issue, that doesn't
>> seem to be the case anymore: looking at releases on [3] and [4]
>> it looks like ungoogled-chromium's latest shipped release matches
>> the latest released chromium version.  Granted, I have noticed in
>> the past for ungoogled-chromium to lag behind the latest release
>> by a week or two, that'd still be better compared to the current
>> situation with respect to the current Firefox/IceWeasel release.
>
> Indeed, Ungoogled have catched up pretty well and is a viable choice
> nowadays.  If it helps get Chromium into Guix I'm all for it.

I think it would be much better to explicitly use an upstream project
that is specifically focused on ongoing removal of spyware, than to rely
on Guix developers to do this ongoing work and to update our list of
cherry-picked patches with every update.

There is likely to come a time when our attention is elsewhere, and it
will sometimes be tempting to update our Chromium package without
properly researching whether additional spyware-removal patches should
be added.

What do you think?

Thanks for all of your hard work on this, Marius.

      Mark

  reply	other threads:[~2018-09-02 16: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
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 [this message]
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=87pnxvyioj.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=clement@lassieur.org \
    --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).