From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [Package Request] SeaMonkey
Date: Sat, 01 Feb 2020 21:50:44 +0100 [thread overview]
Message-ID: <20200201205044.S1AZw0ptcrVnxtRVsAu702HNyfsN5MQiZ3_GR8X90C0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17772@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/issues/17772#issuecomment-581068050
Comment:
Yeah, I have nothing about eventually having this included, but not while it's on an old codebase. Maintaining a web browser is a massive task, and I assume seamonkey does not have a lot of developers to spare, and zero-days are a thing even in mainline Firefox. While some people may claim that distro should not care and it's the user's responsibility, ultimately it's distro maintainers who are blamed when something bad happens, and it's the distro's responsibility to curate what is included in the repository and provide some degree of quality control. Seamonkey has previously announced that they'd be rebasing onto a modern core.
next prev parent reply other threads:[~2020-02-01 20:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 17:36 [ISSUE] Seamonkey voidlinux-github
2019-12-28 1:35 ` [Package Request] SeaMonkey voidlinux-github
2019-12-29 11:29 ` voidlinux-github
2020-01-06 17:48 ` voidlinux-github
2020-01-29 14:28 ` voidlinux-github
2020-01-29 14:29 ` voidlinux-github
2020-01-29 16:46 ` voidlinux-github
2020-02-01 17:20 ` voidlinux-github
2020-02-01 20:50 ` voidlinux-github [this message]
2020-02-29 22:23 ` userabc123xyz
2020-05-06 22:56 ` userabc123xyz
2020-05-06 23:00 ` userabc123xyz
2020-05-06 23:00 ` userabc123xyz
2020-05-06 23:00 ` userabc123xyz
2020-05-06 23:03 ` userabc123xyz
2020-07-19 16:57 ` xianwenchen
2021-03-03 6:01 ` rogerxxxx
2024-06-14 13:43 ` [ISSUE] [CLOSED] " ahesford
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=20200201205044.S1AZw0ptcrVnxtRVsAu702HNyfsN5MQiZ3_GR8X90C0@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).