From: autoteelar <autoteelar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: LibreWolf
Date: Sat, 18 Sep 2021 17:07:21 +0200 [thread overview]
Message-ID: <20210918150721.Fgx51cp2nctsVmrGFMikAUqkFlnQR_Mt2I4VjJI8D3A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24393@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
New comment by autoteelar on void-packages repository
https://github.com/void-linux/void-packages/issues/24393#issuecomment-922325529
Comment:
> We have GNU icecat (a.k.a. gnuzilla) and won't add yet another fork of Firefox to the repository.
> It takes just too much man and machine power to maintain and build all the browsers.
well, i tried but
Package 'icecat' not found in repository pool.
librewolf i heard is better anyways, and well why be at least a little open about it? being so closed like that doesn't sound like an open source community to me, just because you don't want to maintain it doesn't mean someone else wont want to, and the fact theres multiple duplicate tickets open about it just means theres that much want for it it. and it seems 90% of people myself included abstain against using flatpaks aswell.
next prev parent reply other threads:[~2021-09-18 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 18:42 [ISSUE] " handow23
2020-08-20 18:47 ` ericonr
2020-08-20 18:47 ` pullmoll
2020-08-20 19:16 ` Piraty
2020-08-20 19:16 ` [ISSUE] [CLOSED] " Piraty
2020-08-20 19:16 ` Piraty
2021-09-18 15:07 ` autoteelar [this message]
2021-09-18 15:18 ` q66
2021-09-27 15:05 ` Dko1905
2021-09-27 15:20 ` q66
2021-09-27 15:22 ` q66
2021-09-27 15:28 ` sgn
2021-09-27 16:03 ` autoteelar
2021-09-27 16:10 ` q66
2021-09-11 6:28 [ISSUE] Package Request: LibreWolf apirusKde
2021-09-11 8:31 ` paper42
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=20210918150721.Fgx51cp2nctsVmrGFMikAUqkFlnQR_Mt2I4VjJI8D3A@z \
--to=autoteelar@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).