This directory contains the configuration files needed to create a Flatpak package for qSpeak and submit it to Flathub.
org.qforge.qspeak.yml- The main Flatpak manifest fileorg.qforge.qspeak.metainfo.xml- Application metadata for Flathubflatpak-README.md- This file
Before building the Flatpak, you need to install the required tools and runtime:
On Arch Linux/Manjaro:
sudo pacman -S --needed flatpak flatpak-builderOn Ubuntu/Debian:
sudo apt install flatpak flatpak-builderOn Fedora:
sudo dnf install flatpak flatpak-builderflatpak install flathub org.gnome.Platform//46 org.gnome.Sdk//46- Clone or download these configuration files
- Make sure both
org.qforge.qspeak.ymlandorg.qforge.qspeak.metainfo.xmlare in the same directory - Build the Flatpak:
flatpak-builder --repo=local-repo build-dir org.qforge.qspeak.yml --force-clean- Install the locally built Flatpak:
flatpak --user remote-add --no-gpg-verify local-repo local-repo
flatpak --user install local-repo org.qforge.qspeak- Run the application:
flatpak run org.qforge.qspeakAfter installation, test that:
- The application launches correctly
- All UI elements work as expected
- File permissions are appropriate
- The application can access necessary system resources
To submit qSpeak to Flathub:
- Fork the Flathub repository on GitHub
- Clone your fork:
git clone --branch=new-pr git@github.com:your_username/flathub.git cd flathub - Create a new branch:
git checkout -b qspeak
- Copy the manifest files to the repository:
cp org.qforge.qspeak.yml org.qforge.qspeak.metainfo.xml /path/to/flathub/
- Commit and push your changes:
git add org.qforge.qspeak.yml org.qforge.qspeak.metainfo.xml git commit -m "Add qSpeak application" git push origin qspeak - Open a pull request against the
new-prbranch on the Flathub repository
- The manifest uses the GNOME 46 runtime which includes all standard dependencies
- Network access is enabled for potential online features
- Home directory access is granted for saving recordings
- The application ID
org.qforge.qspeakfollows the reverse domain naming convention - Make sure to update the version in the metainfo.xml file when releasing new versions
If you encounter issues:
- Check the build logs for any missing dependencies
- Verify that all file paths in the manifest match the actual deb package structure
- Test the application in the Flatpak runtime to ensure all features work
- Consult the Flatpak documentation for advanced configuration options
For Flathub-specific issues, refer to the Flathub documentation.