FLATPAK-BUILD-BUNDLE(1)

💖 flatpak-build-bundle — it's giving "one file, whole app" 💖

okay bestie, welcome to flatpak-build-bundle(1), a lil page from the flatpak manual, section 1 (that's the "user commands" section, iykyk). she's a build-tool girlie and she's about to hand you a single file containing a whole app or runtime. no cap. 🎀

---

✨ NAME ✨

flatpak-build-bundle — Create a single-file bundle from a local repository

---

✨ SYNOPSIS ✨

flatpak build-bundle [OPTION...] LOCATION FILENAME NAME [BRANCH]

---

✨ DESCRIPTION ✨

So here's the tea ☕: this command creates a single-file named FILENAME for the application (or runtime) named NAME sitting in the repository at LOCATION. If you also pass a BRANCH, then that branch of the application is the one that gets used. slay. 💅

The collection ID set on the repository at LOCATION — if it's set — will be used for the bundle. (if it's not set, it's not set, that's just how it is 🫶)

Unless --oci is used, the format of the bundle file is that of an ostree static delta (against an empty base) with some flatpak specific metadata for the application icons and appdata. iconic behavior honestly.

---

✨ OPTIONS ✨

The following options are understood:

• -h, --help — Show help options and exit. short, sweet, helpful. queen behavior. 👑
• --runtime — Export a runtime instead of an application. plot twist: it's not an app this time, it's a runtime.
• --arch=ARCH — The arch to create a bundle for. Wanna know which architectures your host actually supports? Check flatpak --supported-arches. 💻
• --repo-url=URL — The URL for the repository from which the application can be updated. The way this works: installing the bundle will automatically configure a remote for this URL. auto-setup, we love to see it. ✨
• --runtime-repo=URL — The URL for a .flatpakrepo file that contains the information about the repository that supplies the runtimes required by the app. 🧚
• --gpg-keys=FILE — Add the GPG key from FILE (use - for stdin). yes bestie, a literal dash means stdin, that's not a typo. 🔐
• --gpg-homedir=PATH — GPG Homedir to use when looking for keyrings. tell her where the keyrings live 🏠
• --from-commit=COMMIT — The OSTree commit to create a delta bundle from.
• --oci — Export to an OCI image instead of a Flatpak bundle. different format, same drama. 🌈
• --oci-layer-compress=gzip|zstd — Choose how to compress the layers in OCI images. gzip (the default) is universally supported, but zstd compresses faster and results in smaller images. As of 2023, zstd support is present in most major registries. so if you wanna be ✨efficient✨, you know what to do.
• -v, --verbose — Print debug information during command processing. she's chatty and we respect it. 💬
• --ostree-verbose — Print OSTree debug information during command processing. even MORE chatty. the ostree-level lore. 💀

---

✨ EXAMPLES ✨

first one, using the system-wide repo path:

$ flatpak build-bundle /var/lib/flatpak/repo gnome-calculator.flatpak
org.gnome.Calculator stable

second one, same energy but with your own local user repo:

$ flatpak build-bundle ~/.local/share/flatpak/repo
gnome-calculator.flatpak org.gnome.Calculator stable

ok tiny heads-up bestie 🫶 the synopsis is [OPTION...] LOCATION FILENAME NAME [BRANCH] — one line in the synopsis, but in real life your shell might wrap it across two lines like the examples above. it's still the same four-ish arguments, promise. don't panic. 🌸

---

✨ SEE ALSO ✨

go read these too, they're all in the same friend group:

• ostree(1)
• flatpak(1)
• flatpak-build-init(1)
• flatpak-build(1)
• flatpak-build-finish(1)
• flatpak-build-import-bundle(1)
• flatpak-build-update-repo(1)

---

and that's the whole page, bestie!! 🦋 this manual came to you from the flatpak project, and it lives in section 1 of the manual set (that's FLATPAK BUILD-BUNDL(1) if you're keeping score 📝). go build a bundle, you're gonna eat. 💖✨ no cap, periodt. 💅