Add documentation for various module source types

Reference the new docs where possible
flatpak · May 28, 2024 · e1efeca · e1efeca
1 parent 4e8eb50
commit e1efeca
Show file tree

Hide file tree

Showing 4 changed files with 576 additions and 21 deletions.
diff --git a/docs/building.rst b/docs/building.rst
@@ -17,5 +17,6 @@ before reading this section.
    dependencies
    flatpak-builder
    manifests
+   module-sources
    sandbox-permissions
    guides
diff --git a/docs/conventions.rst b/docs/conventions.rst
@@ -179,26 +179,6 @@ The distribution usually appends those paths to ``$XDG_DATA_DIRS`` on
 host when installing the ``flatpak`` package. Unless a desktop file is
 exported by Flatpak, host applications cannot access it.
 
-Exporting through extra-data
-----------------------------
-
-.. note::
-
-  Note, that when creating a Flatpak package for a software store like
-  Flathub or when composing the metadata with appstreamcli, desktop files
-  and icons must not be placed in ``/app/extra/export/`` and instead
-  should go to the proper locations documented above.
-
-Files downloaded through ``extra-data`` are only downloaded when installing, as such they aren't yet available for ``flatpak-builder`` to automatically export during the build process.
-
-When using ``extra-data``, place any files that must be exported under this location::
-
-  /app/extra/export/share/
-
-For example, if GNOME Dictionary used ``extra-data`` to download a 96x96 icon this would be its path::
-
-  /app/extra/export/share/icons/hicolor/96x96/apps/org.gnome.Dictionary.png
-
 Technical conventions
 ---------------------
 

diff --git a/docs/manifests.rst b/docs/manifests.rst
@@ -164,7 +164,7 @@ types include:
    include archive or package files
 
 Different properties are available for each source type, which are listed
-in the :doc:`flatpak-builder-command-reference`.
+in the :doc:`module-sources`.
 
 Supported build systems
 ```````````````````````