We distribute Bitwig Studio on flathub, and when a customer buys Bitwig Studio, he owns a given version for life.
On top of publishing to flathub, we would also have an archive directory on our website so a user can download any older version from us as a
If I understood correctly, after 2 years a runtime is not maintained anymore.
I totally understand that at some point in time a runtime is not maintained anymore, this is fine.
We want to be sure that if we produce
com.bitwig.BitwigStudio-4.1.5.flatpak today, it will still be installable in 5 years. And for that we wonder if old and unmaintained runtime are still available? If the user installs the package, will he get a warning “You’re about to install an unsupported runtime”? Or will the installation fail saying “Your package depends upon a runtime which isn’t available”?
Another options for us could be:
flatpak install ./com.bitwig.BitwigStudio-4.1.5.flatpak --force-runtime=XXX. This may work as there is a chance that a newer runtime is backward compatible and Bitwig Studio itself has a small surface of dependencies toward the runtime.
What is in your opinion the best way to deal with long term support of a package?
Thank you for your help.