From cbaebf811e6edb79279f72950b2d63189be314d3 Mon Sep 17 00:00:00 2001 From: David Rheinsberg Date: Fri, 11 Oct 2024 10:07:40 +0200 Subject: [PATCH] docs/DESKTOP_ENVIRONMENT: clarify usage The part is optional in the naming scheme of application units. However, this is only true for service files. Scope units must include the part, otherwise it would be impossible to parse: The schema would be: `app[-]-[-].scope` in which case a two-part name would be impossible to parse, since it is unclear whether the launcher of the random bit where omitted. --- docs/DESKTOP_ENVIRONMENTS.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/DESKTOP_ENVIRONMENTS.md b/docs/DESKTOP_ENVIRONMENTS.md index ebf46949346..a42efd6791e 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. + * `` 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 `` 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 -- 2.47.3