[ISSUE] Document the "no firefox fork package" policy

[ISSUE] Document the "no firefox fork package" policy

[vincele]

[-- Attachment #1: Type: text/plain, Size: 827 bytes --]

New issue by vincele on void-packages repository

https://github.com/void-linux/void-packages/issues/44281

Description:
I was searching for librewolf to try it, and after a while found the bunch of closed / won't fix issues.

After reading a few of them and seeing the irritation they seem to cause, I then searched into the FAQ to see if this fact is documented in there and did not find anything.

I think this policy (looks like it's not only for firefox) could be documented somewhere, to help alleviate the duplicated issues and questions. And the invitation to use flatpacks instead, could also be explained at the same place.

FYI: I tried the nix package manager on top of void, and its librewolf is usable. Too bad the nix void package is not working on musl x86_64 void (see #37382).

Did I miss something ?

Re: Document the "no firefox fork package" policy

[mhmdanas]

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

New comment by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/issues/44281#issuecomment-1577181136

Comment:
This is mentioned in [CONTRIBUTING.md](https://github.com/void-linux/void-packages/blob/aa13922f5c0aa55184c364c1bbf7075b3b26c0a9/CONTRIBUTING.md):

> Browser forks, including those based on Chromium and Firefox, are generally not accepted.
Such forks require heavy patching, maintenance and hours of build time.

Re: Document the "no firefox fork package" policy

[vincele]

[-- Attachment #1: Type: text/plain, Size: 287 bytes --]

New comment by vincele on void-packages repository

https://github.com/void-linux/void-packages/issues/44281#issuecomment-1577242511

Comment:
Ah, yes, OK, my bad.

But this does not look like the most visible place, especially wrt non-contributors requesting for package additions...

Re: Document the "no firefox fork package" policy

[vincele]

[-- Attachment #1: Type: text/plain, Size: 310 bytes --]

New comment by vincele on void-packages repository

https://github.com/void-linux/void-packages/issues/44281#issuecomment-1577242511

Comment:
Ah, yes, OK, my bad. Should have grepped...

But this does not look like the most visible place, especially wrt non-contributors requesting for package additions...

Re: Document the "no firefox fork package" policy

[mhmdanas]

[-- Attachment #1: Type: text/plain, Size: 217 bytes --]

New comment by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/issues/44281#issuecomment-1577321309

Comment:
Perhaps, but that's where the package requirements happen to be for now.

Re: [ISSUE] [CLOSED] Document the "no firefox fork package" policy

[vincele]

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

Closed issue by vincele on void-packages repository

https://github.com/void-linux/void-packages/issues/44281

Description:
I was searching for librewolf to try it, and after a while found the bunch of closed / won't fix issues.

After reading a few of them and seeing the irritation they seem to cause, I then searched into the FAQ to see if this fact is documented in there and did not find anything.

I think this policy (looks like it's not only for firefox) could be documented somewhere, to help alleviate the duplicated issues and questions. And the invitation to use flatpacks instead, could also be explained at the same place.

FYI: I tried the nix package manager on top of void, and its librewolf is usable. Too bad the nix void package is not working on musl x86_64 void (see #37382).

Did I miss something ?

Re: Document the "no firefox fork package" policy

[mhmdanas]

[-- Attachment #1: Type: text/plain, Size: 288 bytes --]

New comment by mhmdanas on void-packages repository

https://github.com/void-linux/void-packages/issues/44281#issuecomment-1577414386

Comment:
Also, note that the user is pointed to the package requirements in the package request template anyway, so this is a non-issue in that context.