Dima Pasechnik wrote: > # WARNING -- if you add a package here, also add it to > # the gap_reset_workspace() command in > # <SAGE_ROOT>/src/sage/interfaces/gap.py > > but AFAICS not all of the GAP packages from the current optional > gap_packages package are actually listed / treated there, no idea why. > > > Otherwise it *may* perhaps help to delete all old GAP workspaces (by > default in $HOME/.sage/gap/) *before* (re)starting Sage, then calling > gap_reset_workspace() again. > > If I'm not mistaken, you could afterwards load the GAP packages you > want, before calling gap_reset_workspace() once again, in order to make > them part of your saved workspace. > > > there are GAP packages that break libGAP (see my other message in this > thread), so you cannot allow a GAP workspace with them to be used by libGAP.
Well, both seem to have separate workspaces (workspace-XXX vs. libgap-workspace-XXX, not always "in sync", i.e., not always both present), so it should be possible to exclude "critical" GAP packages from libGAP's. With some effort, it would IMHO also be possible to even automatically blacklist packages (completely, or just for use with libGAP). -leif > This probably can be fixed, or libGAP can be made compatible with them > (although the latter is perpetuating what is basically a GAP fork). > > Dima -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
