Op 09-07-2022 om 16:01 schreef Eric Schirra:
Am Samstag, 9. Juli 2022, 14:41:42 CEST schrieb Stefan Brüns:
On Freitag, 8. Juli 2022 23:19:22 CEST Carlos E. R. wrote:
Does this mean that the flatpack of calibre would contain inside the proper version of python? Would this not mean that we would need powerful computers with huge hard disks, to have this pentaplication of libraries, and a corresponding large CPU to cope with all this?
It would be the end of using Linux on old computers. If this is so, I have to find another distro.
Each Python 3.x would probably be a flatpak runtime. On top of that you could have an "extra" (or whatever) runtime layered on top, which includes a set of very common dependencies/python modules.
You can think of flatpak runtimes as somewhat coarse-granular set of packages. There likely is *some* waste due to duplication or not strictly required depencies, but in most cases this is neglegible.
The calibre flatpak than only has to bring additional modules which are not included in the runtimes below, and are very often only used by this single application.
But that's a bit naive. Calibre needs about 40 python modules. If we assume that it would work with the "flatpack collection packages", then surely no one will first search these "collection packages" for possibly needed python modules. That's a lot of work. So much more work and therefore much more time. And with every other program I have to do that again.
Calibre will be a challenge, if possible at all. At Flathub they don't build it from source, but repackage the build that is provided by the developer (although there is an effort to make it build from source). See the bugreport: https://github.com/flathub/com.calibre_ebook.calibre/issues/17 Still, with flatpak we would be able to provide a version for Leap, even if it is difficult. And the work done at flathub can provide a starting point, maybe. Anyway, thanks Eric for work you do on calibre. Cor