unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Firefox 52's end of life, packaging Chromium
Date: Wed, 29 Aug 2018 23:25:34 +0200	[thread overview]
Message-ID: <CAL7_Mo_G8CRCPhKu1XSvU2SoJ5CJmHB2zY2cq_ZYCxYpzcnqEg@mail.gmail.com> (raw)
In-Reply-To: <87ftyx35pw.fsf@lassieur.org>

Hello all :]

I will confess that if I use Ubuntu today, long story short, it's
because of the web browser.
I could not find my way around patchelf so I gave up and installed Ubuntu.

The matter relates to me a lot!

Le mer. 29 août 2018 à 11:03, Clément Lassieur <clement@lassieur.org> a écrit :
>
> 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).

Here the list of known issues:
https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix;include=subject:epiphany

>
>
> 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


Not having access to a recent web browser can be a pain. That said
they are alternatives.
Many that don't involve more guix energy to be sucked into supporting
chromium or firefox
which I predict to be really painful in the future. Web browsers are
not just about getting the
initial package inside the main repository. It's a lot of pain.

What I think is that we choose our battle wisely. If this discussion
did not pop on the mailling list
I would be doing something else. Nevermind.

Let's choose our battle wisely. I want to remind that the core of the guix users
are GNU followers and are also anything but pro web or pro web browser or a
variation of that. I don't say every GNU follower is against the www.
It's not the
core of potential guix users

I won't help to bring firefox or chromium because I think even if done
ethically will
be a worthless time sink.

Let's be rational, and try to answer the following questions:

1) What firefox or chromium are useful for compared to other graphical
web browsers?

2) What will chromium bring to guix and guix developers that they
can't do otherwise?

3) What are the minimal features for a graphical web browser to be
useful for a guix developer?


I was going to say, let's find or build a minimal browser that use
qtwebkit but even that is
worthless because several people reported performance build issues
about it on IRC.

Sorry, it seems like a worthless timesink to me. The only thing
worthwhile is to build a
web browser using Guile but that will take several years before one
can use it instead
of Chromium... I still don't know why people would want to use that
except for SaaSS
stuff.

They are workarounds.

---

> The Internet was done so well that most people think of it as a
> natural resource like the Pacific Ocean, rather than something that
> was man-made. When was the last time a technology with a scale like
> that was so error-free? The Web, in comparison, is a joke. The Web was
> done by amateurs.

Alan Kay.

  parent reply	other threads:[~2018-08-29 21:33 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 [this message]
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=CAL7_Mo_G8CRCPhKu1XSvU2SoJ5CJmHB2zY2cq_ZYCxYpzcnqEg@mail.gmail.com \
    --to=amirouche.boubekki@gmail.com \
    --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).