Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package request: floorp #50951

Open
zukas97 opened this issue Jun 23, 2024 · 6 comments
Open

Package request: floorp #50951

zukas97 opened this issue Jun 23, 2024 · 6 comments
Labels
request Package request

Comments

@zukas97
Copy link

zukas97 commented Jun 23, 2024

Package name

floorp

Package homepage

https://floorp.app/en

Description

Floorp is a highly customizable browser based on firefox's gecko engine.

Does the requested package meet the package requirements?

Compiled

Is the requested package released?

Yes

@zukas97 zukas97 added the request Package request label Jun 23, 2024
@classabbyamp
Copy link
Member

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

@Luciogi
Copy link
Contributor

Luciogi commented Jun 24, 2024

Get tar files from them extract it and use it, just manually update them

@cplir-c
Copy link

cplir-c commented Jun 24, 2024

Classabbyamp quoted the Contibuting.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 or 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.

@zukas97
Copy link
Author

zukas97 commented Jun 25, 2024

Classabbyamp quoted the Contibuting.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 or 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.

@classabbyamp
Copy link
Member

we won't accept a binary package when source is available

@hunt3r0one
Copy link

You can try my template here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
request Package request
Projects
None yet
Development

No branches or pull requests

5 participants