Opened 5 years ago

Last modified 5 months ago

#21493 new enhancement

Make an autotools-based new upstream package for rubiks

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-wishlist
Component: packages: standard Keywords: sd111
Cc: tmonteil, embray, jdemeyer, jhpalmieri Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

From https://trac.sagemath.org/ticket/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://trac.sagemath.org/ticket/21486?cnum_edit=9#comment:9:

Replying to tmonteil:

Replying to mkoeppe:

"Someone" should just step up and make a proper autotools package, which can serve as the upstream for the sage package. See also #21103 comment 8.

Well, rubiks is a bitrotting bundle of 3 packages, for which i am not sure upstream could be contacted (the links provided in SPKG.txt are dead). So, it will require the additional work of writing 3 fresh spkgs while i am not sure their code will evolve.

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.

Change History (2)

comment:1 Changed 5 years ago by embray

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.

comment:2 Changed 5 months ago by mkoeppe

  • Keywords sd111 added

Hoping we can make progress on this ticket this week - https://wiki.sagemath.org/days111

Note: See TracTickets for help on using tickets.