From: "Clément Lassieur" <clement@lassieur.org>
To: guix-devel@gnu.org
Subject: Firefox 52's end of life, packaging Chromium
Date: Wed, 29 Aug 2018 11:03:07 +0200 [thread overview]
Message-ID: <87ftyx35pw.fsf@lassieur.org> (raw)
Hi,
Firefox 52 isn't supported anymore upstream[1] and we don't have a
package for Firefox 60. Currently the only alternative is Epiphany but
it's close to unusable (it crashes every 5 minutes, and sometimes
freezes my computer).
So the question is: can we push the Chromium package? I've read it's
almost ready[2]. It's probably far better than everything we have,
despite not being totally 'finished'. Maybe we can add what's left to
do as a TODO and fix the package later?
What do you think?
Clément
[1]: https://blog.mozilla.org/futurereleases/2018/01/11/announcing-esr60-policy-engine/
[2]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28004#233
next reply other threads:[~2018-08-29 9:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 9:03 Clément Lassieur [this message]
2018-08-29 15:24 ` Firefox 52's end of life, packaging Chromium 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
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=87ftyx35pw.fsf@lassieur.org \
--to=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).