@iosonofabio You’re an Arch Linux user, right?
I noticed that Arch always picks up new igraph releases exceptionally fast. Arch Linux - igraph 0.9.0-1 (x86_64) 0.9.0 appeared within hours of release. It also appears that Arch links
python-igraph to an external
igraph (instead of using a private version). At least
pyhon-igraph is listed as a dependent of
igraph here. If so, this quick update has most certainly broken python-igraph in Arch Linux. @iosonofabio can you check if it’s really broken, and if yes, talk to someone at Arch Linux?
This is why I am so strongly against linking high-level interfaces to the C core dynamically.
I’d like to propose that:
- By default, the Python interface should link to a guaranteed-to-match the C core statically. @tamas is this already the case? Linking to an external C core dynamically should be an opt-in feature, to be enabled by distro/package maintainers on their own responsibility. They then need to ensure that the two packages always match.
- These issues should be clearly documented. We do now have a guide for package maintainers.
For package management systems that use a rolling release model it is just not feasible not to decouple the high-level igraph interfaces from the C core, otherwise things will break. We don’t have facilities to allow multiple C core versions on the same systems. Thus the issue affects basically all package management systems that are not tied to a Linux distro (MacPorts, Homebrew, vcpkg, etc.) as well as a bunch of Linux distros (notably Arch).