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

installing-pulsar: Add instructions for Gentoo #213

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

zhuyifei1999
Copy link

I added the build files to the Gentoo GURU overlay yesterday (gentoo/guru@2a8c35b). I'll try my best to keep it up to date and I think that'll help adoption.

I added the build files to the Gentoo GURU overlay
yesterday [1]. I'll try my best to keep it up to date
and I think that'll help adoption.

[1] gentoo/guru@2a8c35b
@Daeraxa
Copy link
Member

Daeraxa commented May 22, 2023

I do appreciate the contribution but I'm not currently sure if we want to merge this. Basically if we add this into the documentation we are "officially" supporting it - currently the only things we officially support is on the main downloads page - in terms of package managers for example we only support two currently and each one went through voting and discussions to make sure that we were 1) Comfortable with the implementation and 2) happy and knowledgeable enough to support it when we need to update it or if something goes wrong.

I know you said you will be around but I feel we need some level of redundancy - currently the "bus factor" means if you stopped supporting it then we are a bit stuck.

The issue with Gentoo is that I'm not sure we have anyone on the team at the moment who uses it and we would need to be able to understand and make sure we understand the process of updating it. For example it seems each regular release would need a new PR for an updated ebuild?

So far I've been adding stuff to https://github.com/orgs/pulsar-edit/discussions/77 to keep track of community maintained distributions - maybe we need a new page on the website for community maintained distributions instead and provide links to it? I already had GURU listed so I can add against that in the short term.

@zhuyifei1999
Copy link
Author

zhuyifei1999 commented May 22, 2023

I know you said you will be around but I feel we need some level of redundancy - currently the "bus factor" means if you stopped supporting it then we are a bit stuck.

Makes sense

For example it seems each regular release would need a new PR for an updated ebuild?

That is correct. The ebuild is mostly version-independent however (like how it uses ${PV} to substitute the version number in the URL) so it's mostly copy the ebuild to a new filename containing a different version number, and test if it works properly. There are some gotchas, such as how it seems to forget the chmod +x on executable (and would break Ctrl-P fully search) and they need to be chmodded+x after files are installed.

So far I've been adding stuff to https://github.com/orgs/pulsar-edit/discussions/77 to keep track of community maintained distributions
I already had GURU listed so I can add against that in the short term.

Awesome!

maybe we need a new page on the website for community maintained distributions instead and provide links to it?

Sounds like a really good idea to me.

In that case feel free to close this PR.

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

Successfully merging this pull request may close these issues.

2 participants