<?xml version="1.0" encoding="UTF-8"?> <component type="addon"> <id>gedit-bookmarks</id> <extends>gedit.desktop</extends> <name>Bookmarks</name> <summary>Easy document navigation with bookmarks</summary> <url type="homepage">https://wiki.gnome.org/Apps/Gedit/ShippedPlugins</url> <url type="bugtracker">https://bugzilla.gnome.org/enter_bug.cgi?product=gedit&component=Plugins</url> <metadata_license>CC0-1.0</metadata_license> <project_license>GPL-2.0+</project_license> </component>
application_name-plugin_name
naming scheme for your addon-id.
.desktop
file.
<name/>
tag, giving the addon a human-readable name.
Note
<name/>
- so you want to use Bookmarks
rather than GEdit Bookmarks
<summary/>
tag follows the basic structure of a <summary/> as described in the specification. It is a required tag for an addon component.
<summary/>
- so you want to use Easy document navigation with bookmarks
rather than Easy document navigation with bookmarks in GEdit
.
<summmary/>
should be less than 101
and more than 8
.
homepage
and bugtracker
. You can omit the <url/>
if it's the same as the upstream project.
homepage
should be a link to the upstream homepage for the addon.
bugtracker
should be a link to the upstream bugtracker.
Note
Warning
&
with &
.
<metadata_license/>
tag is indicating the content license that you are releasing the one metadata file as. This is not typically the same as the project license. By ommitting the license value would probably mean your data would not be incorporated into the distribution metadata. Permissible license codes include:
<project_license/>
tag is indicating the license(s) this addon is released under. Take a look at the specification of the <project_license/> tag for details on how to properly use it.