launch/service: name transient units after desktop-spec #303
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The experimental desktop-integration specification [1] proposes a nameing scheme for the units of desktop applications. Try to implement this scheme. [1] https://systemd.io/DESKTOP_ENVIRONMENTS/ Signed-off-by: David Rheinsberg <[email protected]>
teg
approved these changes
Nov 29, 2022
|
I'm still not sure if we should change this only for activated processes which are applications. If so, how would we classify applications (e.g. look for a corresponding .desktop file)? |
|
@dvdhrm I think it would be good if we just land this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The experimental desktop-integration specification [1] proposes a nameing scheme for the units of desktop applications. Try to implement this scheme.
Cc: @swick #302
[1] https://systemd.io/DESKTOP_ENVIRONMENTS/