Opened 3 years ago

Last modified 5 months ago

#21785 new enhancement

Installation of SAGE_SRC/ext/ in SAGE_LOCAL/share/sage/ext/ should be done by, not build/make/Makefile

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-8.9
Component: build Keywords:
Cc: jdemeyer, embray, fbissey, slelievre Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:


Change History (4)

comment:1 Changed 3 years ago by mkoeppe

  • Cc fbissey added

comment:2 Changed 3 years ago by fbissey

That would actually help me. I see extra potential to this for my jupyter kernel install woes as well (even if I know Jeroen doesn't see it that way).

comment:3 Changed 5 months ago by slelievre

  • Cc slelievre added
  • Milestone changed from sage-7.5 to sage-8.9

There was a reference to this ticket in a "sage-packaging" discussion:

comment:4 Changed 5 months ago by embray

I would add, a lot of the stuff (not necessarily all) in $SAGE_SRC/ext might better belong directly in the sage Python package--in particular any files that are needed for the package itself to function properly. For example you can see in #22626 that I put sage.gaprc, a file required for the libgap module to work, in as "package data".

There are several files in $SAGE_SRC/ext that there's no reason to ever allow to be out of sync with the Python package, and that could be given the same treatment.

For files in $SAGE_SRC/ext in general, that aren't explicitly required from the package (are there any such files) it might be better to move out of src/ entirely?

Note: See TracTickets for help on using tickets.