I’m really excited about Fedora Silverblue and how I could convert my “classical” Fedora workstation to it.
Currently, I’m exploring using Flatpak versions of certain applications instead of their classical RPM counter-parts. And I must say it works well for many applications.
One area where I’m having trouble figuring out how things should work in the new Silverblue landscape is with Flatpak-packaged editor/IDEs in relation to application’s software stacks.
For example, a developer is working on a Python application and wants to use Visual Studio Code (OSS version) from Flathub as his development environment.
org.freedesktop.Sdk/x86_64/1.6 runtime on which the current
app/com.visualstudio.code.oss/x86_64/stable is based on (at the time of writing) provides Python 3.5.2 and Python 2.7.12.
This is serious limitation since two new Python versions were released in the mean time, 3.6 and 3.7, and are available in Fedora “classic” Workstation.
Furthermore, one can’t simply configure VS Code to use the host-installed Python executable with a corresponding Python virtual environment since such attempts fail with:
/home/tadej/.local/share/virtualenvs/temp/bin/python: error while loading shared libraries: libpython3.6m.so.1.0: cannot open shared object file: No such file or directory
More generally, when someone develops an application he usually wants to have complete control of the whole software stack, from the version of the language it uses to all the dependent libraries and their versions.
How does Fedora Silverblue plan to tackle this use case?