# Flathub manifest. Submitted to the Flathub review
# repo ~2 weeks before target launch; the KDE 6.x runtime carries Qt, so the
# app bundles no Qt of its own (packaging/qt-lgpl-checklist.md).
app-id: org.kvit.Notes
runtime: org.kde.Platform
runtime-version: "6.10"
sdk: org.kde.Sdk
command: kvit-notes
finish-args:
  - --share=ipc
  - --socket=wayland
  - --socket=fallback-x11
  - --device=dri
  # Notes live where the user keeps them; a vault is an ordinary folder.
  - --filesystem=home
  # The optional update check, and remote content the reader approves
  # (preview cards, images, media). Nothing is fetched without that
  # approval: EgressPolicy gates every request, so this permission is not
  # what decides whether a note can reach the network. See devel.md
  # "Network egress goes through one policy".
  - --share=network
  # Media blocks (audio/video playback).
  - --socket=pulseaudio
modules:
  - name: kvit-notes
    buildsystem: cmake-ninja
    config-opts:
      - -DCMAKE_BUILD_TYPE=Release
    sources:
      - type: git
        url: https://github.com/kvit-s/kvit-notes.git
        # A tag is mutable: it can be moved to a different commit after
        # submission, so it does not pin what Flathub builds. The commit
        # below is what actually fixes the source, and Flathub requires it
        # for git sources. Both are set by tools/update-flatpak-commit.sh
        # as a step of the release procedure (docs/release-rollback.md);
        # the placeholder is not a real object, so a manifest that reaches
        # a build unpinned fails to fetch rather than building something
        # unintended.
        tag: v1.0.0
        commit: "0000000000000000000000000000000000000000"
    post-install:
      - install -Dm644 packaging/flatpak/org.kvit.Notes.metainfo.xml
        /app/share/metainfo/org.kvit.Notes.metainfo.xml