Newbie question #3: plugin, app, runtimes and flatpakref

[Alec Leamas]

So, I have my base application packaged and it works. In order to sort
things out I have split  the original opencpn distribution into a
package without any plugins at all, and a base plugin intended to be
used by every user (so all plugins are installed the same way).

Following the hextile example this ends up in an application (opencpn)
used as a runtime and a plugin (opencpn-plugin-base) which is a runtime.
If I instruct all users to install both of them it works just fine.

I have tried to explore the path of a single flatpakref for users to
install, running into:

- If I add opencpn as the runtime in opencpn-plugin-base.flatpakref it
fails since it generates a dependeny on a *runtime* called opencpn.

- If I try to build opencpn as a runtime a dependency (wxgtk3) FTBS when
trying to install the locales - it cannot cope with some symlinks in
/usr/share/locale like  yi -> ../../share/runtime/locale/yi/share/yi.
While I probably could patch this, I want the packaging to be simple,
not having to patch an ordinary locales installation.

Questions:

- Is the overall arrangement with an application used as a runtime being
available as /application/my.app/// and the extension being a
/runtime/my.app.extension/// sane?

- Is there any way to have a single flatpakref in this scenario?

- What are the links in /usr/share/locale pointing to /usr/share/runtime
about? Is there any documentation out there?


Thoughts?

--alec