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

Manual.md: recommend keeping systemd units #37395

Merged
merged 1 commit into from Aug 1, 2022

Conversation

CameronNemo
Copy link
Contributor

Closes #32481

[ci skip]

Testing the changes

  • I tested the changes in this PR: N/A

@Chocimier
Copy link
Member

What are possible negative side effects?

@Anachron
Copy link
Contributor

Anachron commented Jun 6, 2022

Also closes #32154

About the side effects:
Some packages do check for systemd service files on runtime and try to start/stop when being found.
So I guess if we packaged them and keep the systemd.service files those programs might cause unexpected behavior on Void.

@CameronNemo
Copy link
Contributor Author

CameronNemo commented Jun 6, 2022

One scenario I had in mind was if there was some configure flag that installed the units but also changed the runtime or dependencies of the package in some way. I did not want packagers feeling like they had to install units in that case, or patch the software to get around it. It is just sort of a generic out, letting the packager know they won't get dinged if they exclude the units.

@Chocimier
Copy link
Member

installed the units but also changed the runtime or dependencies of the package in some way

Okay, please mention this as example in manual.

@CameronNemo
Copy link
Contributor Author

Alright added the examples.

@Chocimier Chocimier merged commit b391af3 into void-linux:master Aug 1, 2022
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.

[RFC] systemd service files
5 participants