From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [feedback request] drop icecat
Date: Mon, 11 Jan 2021 10:24:14 +0100 [thread overview]
Message-ID: <20210111092414.8UzwHLQLpHYrsflnSLwtyTAtrW1GIofd1BUbWazTWIY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27731@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
Closed issue by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/27731
Description:
Void has previously made it policy to avoid introducing random forks of major browsers. Despite that, we still have `icecat` in the repos, which seems to me to be pretty much just `firefox-esr` with altered branding and some custom extensions and changed settings. It is so close to just `firefox-esr` that the project no longer bothers to create their own release tarballs, so the `icecat` template in Void fully relies on custom tarballs created by @pullmoll, despite it usually also being policy that we package software from official release archives except in special cases.
So the question is, are those changes it brings worthwhile enough to warrant an entire new firefox build (this one even more annoyingly long than the ordinary one, since it has to generate the localization packages from scratch, which takes a significant chunk of the overall time)? And if those changes are in fact worthwhile, why can't they be done externally to our standard firefox build, in form of config tweaks and custom installable extensions?
This whole thing seems rather puzzling to me. One thing I heard raised as an advantage is that icecat has its own home directory path, so it doesn't conflict with mainline non-esr firefox, but that sounds more like an excuse than anything else to me.
@void-linux/pkg-committers
next prev parent reply other threads:[~2021-01-11 9:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 5:31 [ISSUE] " q66
2021-01-07 6:17 ` Vaelatern
2021-01-07 6:20 ` the-maldridge
2021-01-07 6:46 ` pullmoll
2021-01-07 6:48 ` pullmoll
2021-01-07 6:48 ` the-maldridge
2021-01-07 6:51 ` pullmoll
2021-01-07 6:52 ` the-maldridge
2021-01-07 13:52 ` ericonr
2021-01-07 14:00 ` q66
2021-01-07 19:43 ` uzr123x
2021-01-10 23:43 ` tibequadorian
2021-01-10 23:44 ` tibequadorian
2021-01-11 9:12 ` travankor
2021-01-11 9:24 ` the-maldridge
2021-01-11 9:24 ` the-maldridge [this message]
2021-01-11 9:32 ` pullmoll
2021-01-11 9:33 ` pullmoll
2021-01-11 9:34 ` the-maldridge
2021-01-11 12:57 ` q66
2021-01-19 10:00 ` uber97
2021-01-19 10:01 ` the-maldridge
2021-01-27 2:14 ` tarkov2213
2021-01-27 2:16 ` the-maldridge
2021-01-27 3:08 ` tarkov2213
2021-01-27 3:09 ` tarkov2213
2021-01-27 3:11 ` tarkov2213
2021-01-27 3:37 ` ahesford
2021-01-27 4:10 ` tarkov2213
2021-01-27 4:15 ` tarkov2213
2021-01-27 4:17 ` ahesford
2021-01-27 13:01 ` tibequadorian
2021-01-27 13:07 ` tibequadorian
2021-01-27 13:15 ` Gottox
2021-01-27 17:51 ` ericonr
2021-01-27 17:53 ` [ISSUE] [CLOSED] " pullmoll
2021-01-27 18:38 ` q66
2021-02-01 17:48 ` Raffadiely
2021-02-01 17:48 ` Raffadiely
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=20210111092414.8UzwHLQLpHYrsflnSLwtyTAtrW1GIofd1BUbWazTWIY@z \
--to=the-maldridge@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).