Attachment 85914 Details for Bug 66608 – spec: system services' service description files have constrained names

[patch] spec: system services' service description files have constrained names

0003-spec-system-services-service-description-files-have-.patch (text/plain), 1.30 KB, created by Simon McVittie on 2013-09-16 13:40:08 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2013-09-16 13:40:08 UTC

Size: 1.30 KB

patch

obsolete

>From a2f15f69d9ad4ff15b1c1222cdb3e9991654f144 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Mon, 16 Sep 2013 14:33:41 +0100
>Subject: [PATCH 3/4] spec: system services' service description files have
> constrained names
>
>Bug: https://bugs.freedesktop.org/show_bug.cgi?id=66608
>---
> doc/dbus-specification.xml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
>diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml
>index 3903270..b89631a 100644
>--- a/doc/dbus-specification.xml
>+++ b/doc/dbus-specification.xml
>@@ -4652,6 +4652,19 @@
>       </para>
> 
>       <para>
>+        On the well-known system bus, the name of a service description file
>+        must be its well-known name plus <literal>.service</literal>,
>+        for instance
>+        <literal>com.example.ConfigurationDatabase.service</literal>.
>+      </para>
>+
>+      <para>
>+        On the well-known session bus, services should follow the same
>+        service description file naming convention as on the system bus,
>+        but for backwards compatibility they are not required to do so.
>+      </para>
>+
>+      <para>
>         [FIXME the file format should be much better specified than "similar to
>         .desktop entries" esp. since desktop entries are already
>         badly-specified. ;-)]
>-- 
>1.8.4.rc3
>

Actions: View | Splinter Review

Attachments on bug 66608: 82205 | 82206 | 82314 | 82315 | 85914 | 85915 | 85957 | 87276

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.