documentation icon indicating copy to clipboard operation
documentation copied to clipboard

Inform what is available in each runtime

Open prcastro opened this issue 7 years ago • 9 comments

I'm trying to make a flatpak version of OpenShot, and I couldn't find an easy way to inspect what libraries are available in org.kde.Platform or org.kde.Sdk. I would be nice if this kind of information were available in Flathub's webpage or in the Wiki somehow.

prcastro avatar Jan 03 '18 17:01 prcastro

More discover-ability would always be nice but in the short term some useful information:

Actual manifests for everything:

  • https://github.com/KDE/flatpak-kde-runtime/blob/master/org.kde.Sdk.json
  • https://github.com/flatpak/freedesktop-sdk-images/blob/1.6/org.freedesktop.Sdk.json.in

List of pkg-config files: flatpak run --command=pkg-config org.kde.Sdk//5.9 --list-all

Script that could be modified to turn the manifest into a table: https://gist.github.com/TingPing/65509ee3608d82e17dd09ef8c63a3ef1

TingPing avatar Jan 03 '18 20:01 TingPing

Manifests are shipped with the packages as well, so you can see what your installed runtimes have by checking e.g. for gnome: /var/lib/flatpak/runtime/org.gnome.Platform/x86_64/3.26/active/files/manifest.json

mjog avatar Jan 27 '18 03:01 mjog

@TingPing Please could provide links to the gnome runtimes too? I could not find it github.com/flatpak .. I want to check what runtime includes GTK+2 as I intend to create a flatpak for an old gtk+2 application (testing Flatpak as a useful way to revive abandomware!! :-) )

Also would you accept a PR about this feature?

nbenitez avatar Jul 04 '18 13:07 nbenitez

@TingPing Please could provide links to the gnome runtimes too?

https://gitlab.gnome.org/GNOME/gnome-sdk-images

Also would you accept a PR about this feature?

I think we will do this once the move to fdo 1.8 (and thus buildstream) happens as we can have a singular tool to automatically generate this information.

TingPing avatar Jul 15 '18 00:07 TingPing

Hi all,

For 18.08 (1.8), we keep a manifest file in the wiki so t's easy to see what we are shipping along with the versions.

Here: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/wikis/Release-Contents

There is also an issue open in BuildStream to try and automate this process:

  • https://gitlab.com/BuildStream/buildstream/issues/235

adds68 avatar Aug 08 '18 13:08 adds68

Should this be moved to the docs repo?

razzeee avatar Jun 18 '23 12:06 razzeee

Manifests are shipped with the packages as well, so you can see what your installed runtimes have by checking e.g. for gnome: /var/lib/flatpak/runtime/org.gnome.Platform/x86_64/3.26/active/files/manifest.json

I think we should probably document how to do this and add that to the docs. As that seems to be the only solution, that works for every runtime.

razzeee avatar Jun 25 '23 08:06 razzeee

I think we should probably document how to do this and add that to the docs. As that seems to be the only solution, that works for every runtime.

A lot has changed since this comment and I think it has limited value.

Now everything is built with buildstream so the contents of manifest.json are generated from that data instead of flatpak-builder and is a bit less useful.

It also is just a list of "projects" instead of libraries. The command I said at the start is more useful (pkg-config --list-all in the runtime) in a lot of ways. Another interesting command is ldconfig -p which lists all sonames.

TingPing avatar Jun 25 '23 20:06 TingPing

https://docs.flatpak.org/en/latest/available-runtimes.html covers this somewhat, too

wjt avatar Nov 02 '23 13:11 wjt