Postby gawrilow » 21 Oct 2023, 14:44
We tried to find such a hack but we failed. The problem is that the perl interpreter has hidden some vital functions which were necessary for parsing polymake perl code, starting with such elementary things as Matrix<Rational>. They can't be "revealed" from outside without modifying the perl executable itself (resp. its shared library). The only viable solution from the perspective of a package maintainer is to provide packages with perl 5.36 and a dozen of CPAN modules requiring binary compatibility (like Term::ReadLine::Gnu) in the corresponding older versions, and declare them as prerequisites for polymake package. python community used to provide packages with various versions of python 2 and 3 in parallel for quite a few years until venv became popular and they decided that all relevant modules finally managed to migrate to python 3. But obviously, it's a completely different level of importance which would justify such substantial maintenance efforts, that's not given for a small niche product like polymake.