From: zukas97 <zukas97@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: floorp
Date: Tue, 25 Jun 2024 14:01:07 +0200 [thread overview]
Message-ID: <20240625120107.AA22023514@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50951@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
New comment by zukas97 on void-packages repository
https://github.com/void-linux/void-packages/issues/50951#issuecomment-2188753451
Comment:
> Classabbyamp quoted the [Contibuting.md](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md) document that the issue template has us read.
>
> I think that section means that Chromium and Firefox forks won't be accepted other than in the unlikely case that there's a strong enough reason for the Void Linux maintainers to put many hours into adapting/updating the respective [Firefox patches](https://github.com/void-linux/void-packages/tree/master/srcpkgs/firefox/patches) or [Chromium patches](https://github.com/void-linux/void-packages/tree/master/srcpkgs/chromium/patches) and ensuring the package builds and works properly with the rest of the system. In addition to the base maintainer burden, building Firefox takes a few hours and lots of computing resources (in my opinion; about 8GiB RAM), making it much harder (slower) to test whether the patches and the browser worked properly.
you wouldn't need to recompile floorp. they release a binairy tarball as an option. Someone would just need to package it.
next prev parent reply other threads:[~2024-06-25 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 12:16 [ISSUE] " zukas97
2024-06-23 15:19 ` classabbyamp
2024-06-24 9:28 ` Luciogi
2024-06-24 23:43 ` cplir-c
2024-06-25 12:01 ` zukas97 [this message]
2024-06-25 15:07 ` classabbyamp
2024-06-26 18:28 ` hunt3r0one
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=20240625120107.AA22023514@inbox.vuxu.org \
--to=zukas97@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).