Thank you both for your answers. I think what I will do for now is add
QuaGroup to gap_packages, which I think will be the easiest thing for me to
implement the interface I want, and liealgdb to database_gap. I will also
add François's instructions to the top-level Sage doc for the trivial to
i
There are few GAP packages, one of them io, which need GAP kernel extensions
built (which are some kind of shared libraries). I am not sure whether this
works with users building GAP extensions for a systemwide GAP install.
Dima
--
You received this message because you are subscribed to the Go
> On 26/06/2016, at 17:22, Travis Scrimshaw wrote:
>
> The only method I know to add GAP packages is here:
> https://wiki.sagemath.org/InstallingGapPackages. So at the very least, I
> would like to see an "official" policy and instructions (i.e., in the main
> documentation).
I see. This
> On 25/06/2016, at 16:39, Travis Scrimshaw wrote:
>
> Hey all,
>So I am wanting to do implement an interface to the optional GAP package
> QuaGroup, which will require another optional Sage package. Yet there are
> also a number of other GAP packages that might be useful to a number of
>
Hey all,
So I am wanting to do implement an interface to the optional GAP package
QuaGroup, which will require another optional Sage package. Yet there are
also a number of other GAP packages that might be useful to a number of
people (e.g., SLA, hecke, liealgdb, all of the various HomAlg pkg
