Am Thu, Jul 16, 2026 at 11:25:19AM +0200 schrieb Hugo Buddelmeijer: > My take-home from Konrad's article: having one package be more 'modern' and > 'better' than another, by no means imply that the other package is 'broken' > and needs to be 'fixed' in the name of progress or harmony. > > Luckily, Guix by design makes it feasible, desirable even, to have all these > different packages to co-exist harmoniously all the while being > incompatible.
Well, this is true for C with its dynamic libraries, rpath setting in applications, and sonames (which is why I do not quite feel your pain with the Python packages for my own work, although it comes with its own challenges - five versions of fmt, for instance). But it is made terribly complicated by propagated inputs. Are these handled by your suggestions? For instance I remember sage being unusable for a few weeks because it propagated the Python libraries A and B, which in turn propagated different versions of the Python library C, causing profile collisions. Andreas
