Commit 136b8b8c authored by Sven Herzberg's avatar Sven Herzberg Committed by Simon McVittie

list which parts of the Desktop Entry spec apply to service files

Reviewed-by: default avatarSimon McVittie <simon.mcvittie@collabora.co.uk>
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=19159
parent 75cecfc3
......@@ -39,6 +39,16 @@
</address>
</affiliation>
</author>
<author>
<firstname>Sven</firstname>
<surname>Herzberg</surname>
<affiliation>
<orgname>Imendio AB</orgname>
<address>
<email>sven@imendio.com</email>
</address>
</affiliation>
</author>
</authorgroup>
<revhistory>
<revision>
......@@ -3781,9 +3791,7 @@
<xref linkend="message-bus-types"/>.
</para>
<para>
[FIXME the file format should be much better specified than "similar to
.desktop entries" esp. since desktop entries are already
badly-specified. ;-)] Service description files have the ".service" file
Service description files have the ".service" file
extension. The message bus will only load service description files
ending with .service; all other files will be ignored. The file format
is similar to that of <ulink
......@@ -3793,6 +3801,17 @@
must be namespaced using the same mechanism as messages and service
names.
<para>
[FIXME the file format should be much better specified than "similar to
.desktop entries" esp. since desktop entries are already
badly-specified. ;-)]
These sections from the specification apply to service files as well:
<itemizedlist>
<listitem><para>General syntax</para></listitem>
<listitem><para>Comment format</para></listitem>
</itemizedlist>
<figure>
<title>Example service description file</title>
<programlisting>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment