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

Major difference in systemd syntax compared to NixOS #4715

Open
SohamG opened this issue Nov 29, 2023 · 1 comment
Open

Major difference in systemd syntax compared to NixOS #4715

SohamG opened this issue Nov 29, 2023 · 1 comment

Comments

@SohamG
Copy link

SohamG commented Nov 29, 2023

services = mkOption {

Hello,

I recently wanted to write a user service for myself and noticed that the syntax for systemd stuff is wildly different as compared to upstream NixOS. Honestly, I much prefer the syntax user here but I wish it was better documented.

I was wondering if theres an effort to get this syntax be an option upstream, considering that the ini file generator is quite new. I think its a net detriment to have two different syntax schemes for basically the same thing!

Alternatively, perhaps home-manager could have a "alternative" syntax option supporting the legacy upstream syntax?

Thanks

Copy link

stale bot commented Mar 3, 2024

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

  • If this is resolved, please consider closing it so that the maintainers know not to focus on this.
  • If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

  • If you are also experiencing this issue, please add details of your situation to help with the debugging process.
  • If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

@stale stale bot added the status: stale label Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant