Dima Pasechnik wrote:
> # WARNING -- if you add a package here, also add it to
> # the gap_reset_workspace() command in
> #/src/sage/interfaces/gap.py
>
> but AFAICS not all of the GAP packages from the current optional
> gap_packages package are actually listed / treated t
These four packages seem to be working fine now. I just copied their source
(+quagroup) into the "pkg" directory.
I also had to issue gap_reset_workspace() in sage. I'll do more extensive
tests later, but for now all these packages seem to be fine.
Thanks for your help.
On Saturday, September 1
On Saturday, September 10, 2016 at 10:07:29 PM UTC, multiscalar wrote:
>
> How can I tell if the package I need is safe to add or not?
> These are the ones I'd like to add for now : gbnp,sla,corelg,repsn; are
> these safe?
> if they are, what's the recommended procedure with sage-7.3?
>
The culp
How can I tell if the package I need is safe to add or not?
These are the ones I'd like to add for now : gbnp,sla,corelg,repsn; are
these safe?
if they are, what's the recommended procedure with sage-7.3?
On Saturday, September 10, 2016 at 2:41:35 PM UTC-7, Dima Pasechnik wrote:
>
>
>
> On Saturd
On Saturday, September 10, 2016 at 9:26:02 PM UTC, leif wrote:
>
> multiscalar wrote:
> > Thanks, this is definitely simpler and it worked, but only about half of
> > the packages I use are included. How would I add the other ones?
>
> Well, if you're a bit familiar with Sage / Python and the
multiscalar wrote:
> Thanks, this is definitely simpler and it worked, but only about half of
> the packages I use are included. How would I add the other ones?
Well, if you're a bit familiar with Sage / Python and the shell, take a
look at
build/pkgs/gap_packages/spkg-install (a shell script
