1
0
mirror of https://github.com/systemd/systemd.git synced 2025-08-25 13:49:55 +03:00

Merge pull request #34716 from dvdhrm/pr/derand

Clarify nameing-scheme in DESKTOP_ENVIRONMENT documentation
This commit is contained in:
Lennart Poettering
2024-10-14 11:51:43 +02:00
committed by GitHub

View File

@ -65,11 +65,11 @@ desktop environments should adhere to the following conventions:
instead of the caller starting the process and letting systemd know about it,
is encouraged.
* The RANDOM should be a string of random characters to ensure that multiple instances
of the application can be launched.
It can be omitted in the case of a non-transient application services which can ensure
multiple instances are not spawned, such as a DBus activated application.
* `<RANDOM>` should be a string of random characters to ensure that multiple instances
of the application can be launched. This can be omitted for service files of
non-transient applications, which ensure multiple instances cannot be
spawned. For scope files `<RANDOM>` is mandatory, as the format would be
ambiguous otherwise.
* If no application ID is available, the launcher should generate a reasonable
name when possible (e.g. using `basename(argv[0])`). This name must not
@ -81,7 +81,10 @@ This has the following advantages:
adjusted using desktop environment specific drop-in files.
* The application ID can be retrieved by stripping the prefix and postfix.
This in turn should map to the corresponding `.desktop` file when available
This in turn should map to the corresponding `.desktop` file when available.
Note that this nameing scheme might be a unit alias, so runtime detection
must check the entire name-array of a unit, rather than just its unit ID.
TODO: Define the name of slices that should be used.
This could be `app-<launcher>-<ApplicationID>-<RANDOM>.slice`.