Replies: 2 comments 3 replies
-
Make it easy for this project to be packaged. Don't package yourself, just make it possible. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Would it make sense to just have blocks commented in the PKGBUILD that you are warned need to be uncommented according to the chosen init system? edit I guess this only applies to aur |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I don't expect to get many replies now but I want to leave this open for discussion as to when someone wants to bring this up. Will also reference this discussion on the documentation.
Right now there's absolutely no packaging format for service files. It's not an issue as the project is small but I understand it will end up being really convenient to also get updates for the init system if any important changes requires it, specially on something as important as your init system.
On one hand I could create different packages for each init system, but on the other hand I could just bundle systemd service files by default, I dislike the systemd forced inclusion but at the end of the day is what 99% of the user base uses and what they expect to receive.
Another option is to make the init system packages provide something like
lidm-service
and make it a dependency or optional dependency of the main package, but I can imagine this bringing several dependency issues or some problems for niche setups where one doesn't want to depend on the service files or wants to install multiple (maybe it's still possible though).Idk, if anyone has any good ideas on how to tackle this I'm all ears on how to do this.
Beta Was this translation helpful? Give feedback.
All reactions