Merge pull request #34716 from dvdhrm/pr/derand

Clarify nameing-scheme in DESKTOP_ENVIRONMENT documentation

1 files changed, 9 insertions, 6 deletions

diff --git a/docs/DESKTOP_ENVIRONMENTS.md b/docs/DESKTOP_ENVIRONMENTS.md
index ebf4694934..4f82ce7799 100644
--- a/docs/DESKTOP_ENVIRONMENTS.md
+++ b/docs/DESKTOP_ENVIRONMENTS.md
@@ -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`.