Does Flathub use an internal ID in case packages are renamed?

https://snapcraft.io/docs/snapd-api#heading–find:~:text=%60snap-id%60,snap%20app%20attribute demonstrates that Snapcraft exposes an immutable package identifier.

I ask whether Flathub does for the same reasons explained at https://forum.snapcraft.io/t/can-i-install-a-package-using-its-snap-id/39053?u=beedellrokejulianloc — because in the case a package is renamed (like https://github.com/vector-im/.github/blob/1d586281f08885acaa0284598d3a5dfc32402767/profile/README.md#:~:text=our%20vector-im%20github%20organisation%20has%20been%20renamed%20to%20element-hq. occurs) the package name occasionally changes.

However, my automation code doesn’t need to be readable to the extent that it relies upon transient identifiers.

There is only the well-known app ID. In the event that an app needs to be renamed, the existing one can retired with a link to the new name (eol-rebase).

Flatpak will offer to install the new app upon install or update, and it will rename the app’s data directory in ~/.var/app/. For automation, --assumeyes will make it follow the rename automatically.

1 Like

Does Flathub use an internal ID in case packages are renamed? - #2 by chrisawi

Thanks, @chrisawi. That’s somewhat better, considering that it’s flatpak-native rather than Flathub-specific.