Open mkoeppe opened 7 years ago
Whether 1 or 3 packages, I suggest a fork placed on GitHub to be a good approach, with sage being switched to use the forked project as the upstream.
Changed keywords from none to sd111
Hoping we can make progress on this ticket this week - https://wiki.sagemath.org/days111
From #21103 comment:8: What is considered upstream for this package? Should there be an spkg-src? The links in http://doc.sagemath.org/html/en/reference/interfaces/sage/interfaces/rubik.html and in SPKG.txt are broken.
From https://github.com/sagemath/sage/issues/21486?cnum_edit=9#comment:9:
Replying to tmonteil:
Why 3 spkgs? It would be enough to make 1 new "upstream" source package with an autotools build system and put it on GitHub. That's better than the current situation, with a fictional upstream source package that only exists on sage mirrors.
CC: @sagetrac-tmonteil @embray @jdemeyer @jhpalmieri
Component: packages: standard
Keywords: sd111
Issue created by migration from https://trac.sagemath.org/ticket/21493