com.example.TextViewer.metainfo.xml.in 3.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <component type="desktop-application">
  3. <id>com.example.TextViewer</id>
  4. <metadata_license>CC0-1.0</metadata_license>
  5. <project_license>GPL-3.0-or-later</project_license>
  6. <name>Text-viewer</name>
  7. <summary>Keep the summary shorter, between 10 and 35 characters</summary>
  8. <description>
  9. <p>No description</p>
  10. </description>
  11. <developer id="tld.vendor">
  12. <name>Developer name</name>
  13. </developer>
  14. <!-- Required: Should be a link to the upstream homepage for the component -->
  15. <url type="homepage">https://example.org/</url>
  16. <!-- Recommended: It is highly recommended for open-source projects to display the source code repository -->
  17. <url type="vcs-browser">https://example.org/repository</url>
  18. <!-- Should point to the software's bug tracking system, for users to report new bugs -->
  19. <url type="bugtracker">https://example.org/issues</url>
  20. <!-- Should link a FAQ page for this software, to answer some of the most-asked questions in detail -->
  21. <!-- URLs of this type should point to a webpage where users can submit or modify translations of the upstream project -->
  22. <url type="translate">https://example.org/translate</url>
  23. <url type="faq">https://example.org/faq</url>
  24. <!-- Should provide a web link to an online user's reference, a software manual or help page -->
  25. <url type="help">https://example.org/help</url>
  26. <!-- URLs of this type should point to a webpage showing information on how to donate to the described software project -->
  27. <url type="donation">https://example.org/donate</url>
  28. <!-- This could for example be an HTTPS URL to an online form or a page describing how to contact the developer -->
  29. <url type="contact">https://example.org/contact</url>
  30. <!-- URLs of this type should point to a webpage showing information on how to contribute to the described software project -->
  31. <url type="contribute">https://example.org/contribute</url>
  32. <translation type="gettext">text-viewer</translation>
  33. <!-- All graphical applications having a desktop file must have this tag in the MetaInfo.
  34. If this is present, appstreamcli compose will pull icons, keywords and categories from the desktop file. -->
  35. <launchable type="desktop-id">com.example.TextViewer.desktop</launchable>
  36. <!-- Use the OARS website (https://hughsie.github.io/oars/generate.html) to generate these and make sure to use oars-1.1 -->
  37. <content_rating type="oars-1.1" />
  38. <!-- Applications should set a brand color in both light and dark variants like so -->
  39. <branding>
  40. <color type="primary" scheme_preference="light">#ff00ff</color>
  41. <color type="primary" scheme_preference="dark">#993d3d</color>
  42. </branding>
  43. <screenshots>
  44. <screenshot type="default">
  45. <image>https://example.org/example1.png</image>
  46. <caption>A caption</caption>
  47. </screenshot>
  48. <screenshot>
  49. <image>https://example.org/example2.png</image>
  50. <caption>A caption</caption>
  51. </screenshot>
  52. </screenshots>
  53. <releases>
  54. <release version="1.0.1" date="2024-01-18">
  55. <url type="details">https://example.org/changelog.html#version_1.0.1</url>
  56. <description translate="no">
  57. <p>Release description</p>
  58. <ul>
  59. <li>List of changes</li>
  60. <li>List of changes</li>
  61. </ul>
  62. </description>
  63. </release>
  64. </releases>
  65. </component>