(Create page) |
|||
| (15 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Desktop files == | == Desktop files == | ||
If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws | If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws a window and runs from within that window. Installed .desktop files MUST follow the [http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html desktop-entry-spec] , paying particular attention to validating correct usage of Name, GenericName, [http://standards.freedesktop.org/menu-spec/latest/apa.html Categories] , | ||
[http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify] | [http://www.freedesktop.org/Standards/startup-notification-spec StartupNotify] | ||
entries. | entries. | ||
=== Application independence === | |||
Applications should be installable independently when this is technically feasible. A package should generally not depend on a package containing an application except if it functions as a plug-in for that application. If a source package provides multiple applications, those applications should be packaged in separate subpackages. If a source package provides both a library and also an associated application, that application should be packaged in a subpackage in order to allow other applications to depend on only the library and not the associated application. Installing an application that depends on a library or service should not automatically pull in other applications associated with that library or service. Packages that contain a visible .desktop file (a .desktop file that does not contain the line <code>NoDisplay=true</code>) should generally not have a Requires, Recommends, or Supplements on any other package containing a visible desktop file, directly or indirectly. Use Enhances and Suggests instead. | |||
Revision as of 13:14, 5 June 2017
Desktop files
If a package contains a GUI application, then it needs to also include a properly installed .desktop file. For the purposes of these guidelines, a GUI application is defined as any application which draws a window and runs from within that window. Installed .desktop files MUST follow the desktop-entry-spec , paying particular attention to validating correct usage of Name, GenericName, Categories , StartupNotify entries.
Application independence
Applications should be installable independently when this is technically feasible. A package should generally not depend on a package containing an application except if it functions as a plug-in for that application. If a source package provides multiple applications, those applications should be packaged in separate subpackages. If a source package provides both a library and also an associated application, that application should be packaged in a subpackage in order to allow other applications to depend on only the library and not the associated application. Installing an application that depends on a library or service should not automatically pull in other applications associated with that library or service. Packages that contain a visible .desktop file (a .desktop file that does not contain the line NoDisplay=true) should generally not have a Requires, Recommends, or Supplements on any other package containing a visible desktop file, directly or indirectly. Use Enhances and Suggests instead.