Currently, flatpak-builder seems to assume - in most cases rightfully so - that any build of an extension is for a runtime.
Was hoping to use this to split out an optional extension - DFHack - for the game Dwarf Fortress, since they don't follow anything like the same release schedules.
The documentation here seems sorely lacking, if it's even possible to do what I want at the moment, can't find anything saying either way. And just the specification of how to expose extension points wasn't very well documented either.
{
"app-id": "com.bay12games.DwarfFortress.dfhack",
"branch": "0.43.05",
// What goes in here to make it build as an application extension?
"runtime": "org.gnome.Platform",
"runtime-version": "3.24",
"sdk": "org.gnome.Sdk",
"build-extension": true,
"build-options": {
"prefix": "/app/dfhack"
},
"modules": [
// ...
]
}
Getting complaints to the tune of;
Error: No extension point matching com.bay12games.DwarfFortress.dfhack in runtime/org.gnome.Platform/x86_64/3.24
From @ace13 on May 3, 2017 12:38
Currently, flatpak-builder seems to assume - in most cases rightfully so - that any build of an extension is for a runtime.
Was hoping to use this to split out an optional extension - DFHack - for the game Dwarf Fortress, since they don't follow anything like the same release schedules. The documentation here seems sorely lacking, if it's even possible to do what I want at the moment, can't find anything saying either way. And just the specification of how to expose extension points wasn't very well documented either.
Snippets from manifests;
Getting complaints to the tune of;
Copied from original issue: flatpak/flatpak#762