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.