Add installation page, demodularize, and update #20

Merged
ryanlerch merged 1 commit from master into master 2025-05-07 05:41:19 +00:00

View file

@ -39,6 +39,7 @@ The container version for your stable release should be in the stable branch of
The flatpak/finish-args: section of your container.yaml determines what permissions the application will have.
.Non-sandboxed application, application requires X, and accesses the network
[source,yaml]
----
flatpak:
finish-args: |-
@ -48,6 +49,7 @@ flatpak:
----
.Sandboxed application
[source,yaml]
----
flatpak:
finish-args: |-
@ -56,6 +58,7 @@ flatpak:
----
.Non-sandboxed application, application has wayland support, and uses the host DConf
[source,yaml]
----
flatpak:
finish-args: |-
@ -70,12 +73,13 @@ flatpak:
--env=DCONF_USER_CONFIG_DIR=.config/dconf
----
See http://docs.flatpak.org/en/latest/sandbox-permissions-reference.html and the flatpak-build(1) manual page.
See https://docs.flatpak.org/en/latest/sandbox-permissions.html[Sandbox Permissions] documentation and the https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak-build[flatpak-build(1)] manual page.
=== Renames
Many existing applications in Fedora do not have an application in standard form. You can add keys to your
container.yaml to rename exported resources to match the application ID.
[source,yaml]
....
flatpak:
rename-appdata-file: eog.appdata.xml
@ -104,4 +108,4 @@ The complete list of supported keys from the Flatpak builder manifest file that
* `rename-mime-file`
* `rename-mime-icons`
See the flatpak-manifest(5) manual page for documentation.
See the https://docs.flatpak.org/en/latest/flatpak-builder-command-reference.html#flatpak-manifest[flatpak-manifest(5)] manual page for documentation.