Opened 9 months ago

Last modified 2 months ago

#32711 new defect

gap_console and Gap object are not compatible with the GAP PackageManager

Reported by: culler Owned by:
Priority: minor Milestone: sage-9.7
Component: packages: standard Keywords: GAP PackageManager
Cc: Merged in:
Authors: culler Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by culler)

Ticket #27912 was resolved by adding the PackageManager package to the gap_packages spkg. By default the PackageManager installs packages in ~/.gap. That is an excellent choice, at least for the purpose of the Sage_macOS app, since it does not require writing into the app bundle and thereby corrupting the code signature. However, packages installed that way are only usable with libgap.eval(). Neither gap.load_package nor the gap_console() know to look for packages in that directory. This is easily corrected by adding a -l option to the command used to start gap. I will attach a patch.

Attachments (1)

gap_package.patch (524 bytes) - added by culler 9 months ago.
Add -l option to gap_cmd.

Download all attachments as: .zip

Change History (6)

Changed 9 months ago by culler

Add -l option to gap_cmd.

comment:1 Changed 9 months ago by culler

  • Description modified (diff)

comment:2 Changed 9 months ago by culler

Perhaps it would be better to use ~/.sage/gap in place of ~/.gap . This would presumably require modifying the PackageManager package, however.

comment:3 Changed 9 months ago by culler

  • Authors set to culler

comment:4 Changed 7 months ago by mkoeppe

  • Milestone changed from sage-9.5 to sage-9.6

comment:5 Changed 2 months ago by mkoeppe

  • Milestone changed from sage-9.6 to sage-9.7
Note: See TracTickets for help on using tickets.