flathub / io.github.gtkwave.gtkwave

Flathub

Flathub is the central place for building and hosting Flatpak builds.

Using the Flathub repository

To install applications that are hosted on Flathub, use the following:

flatpak remote-add flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install flathub org.gnome.Recipes

To install applications from the beta branch, use the following:

flatpak remote-add flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo
flatpak install flathub-beta org.godotengine.Godot

For more information and more applications see https://flathub.org

Contributing to Flathub

For information on creating packages or reporting issues please see the contributing page.

Note: this repository is not for reporting issues related to the flathub.org website itself or contributing to its development. For that, go to https://github.com/flathub/website

io.github.gtkwave.gtkwave's Issues

Improved note about current limitations of the Flatpak version

The current note only mentions the transaction example and GLIBC as possible problems:

NOTE: The transaction example doesn't run because of mismatched GLIBC versions.
This is a known issue and limitation of the flatpak version.

But the limitation applies to all external processes, which are now executed inside the sandbox and not on the host. Here is a draft of an improved note:

NOTE: External process and transaction process filters are executed inside the Flatpak sandbox and
don't have access to libraries on the host system. Compiling process filters with a newer GLIBC version
than used in the Flatpak runtime will also cause the filter process to fail. Possible workarounds for this
problem are to use static executables or to compile the process filter using the org.gnome.Sdk Flatpak.

Use flathubbot to detect new GTKWave releases

Some GTKWave users did recently run into problems with the Flatpak version when they tried to load FST files. This issue has been fixed in GTKWave 3.3.115, but the version on Flathub hasn't been updated yet.

I would suggest to add support for the flatpak-external-data-checker to the manifest to automatically detect new releases. The README contains an example how the SF.net RSS feed can be used to detect new tarball releases: https://github.com/flathub/flatpak-external-data-checker#html-checker