1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE appendix [
<!ENTITY % BOOK_ENTITIES SYSTEM "Users_Guide.ent">
%BOOK_ENTITIES;
<!ENTITY % sgml.features "IGNORE">
<!ENTITY % xml.features "INCLUDE">
<!ENTITY % DOCBOOK_ENTS PUBLIC "-//OASIS//ENTITIES DocBook Character Entities V4.5//EN" "/usr/share/xml/docbook/schema/dtd/4.5/dbcentx.mod">
%DOCBOOK_ENTS;
]>
<appendix conformance="133" version="5.0" xml:id="appe-Publican-Users_Guide-Sample_spec_file_for_desktop_menu_package" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
<info>
<title>Sample spec file for desktop menu package</title>
</info>
<para>
The following spec file is an example of how you could package a <firstterm>desktop entry</firstterm> (<filename>.directory</filename>) file and a <firstterm>desktop menu</firstterm> (<filename>.menu</filename>) file in an RPM package for shipping. Refer to <xref linkend="sect-Publican-Users_Guide-Desktop_menu_entries_for_documents" /> for the structure of these files.
</para>
<para>
This example assumes a desktop entry file named <filename>menu-example.directory</filename>, a desktop menu file named <filename>menu-example.menu</filename>, and a readme file named <filename>README</filename> are located in a directory named <filename>menu-example-0</filename> that is archived as <filename>menu-example-0.tgz</filename>.
</para>
<para>
When built, this results in a package named <package>menu-example</package>.
</para>
<programlisting language="RPM Spec"><xi:include href="extras/menu-example.spec" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</appendix>
|
