On Feb 27, 3:37 am, David Joyner <wdjoy...@gmail.com> wrote:
> Just a guess that the skpg install script hardwires the wrong
> directory for the GAP pkgs.
I have been thinking about such build problems and similar things
happen in various other places.
One way to attach this is to have a script called
sage-gap-version
that just returns the name of the current GAP install. This could be
used if there were additional GAP packages in the future and there
would be a good chance that things just keep working and as an added
bonus would likely keep working with older Sage versions using older
GAP releases, i.e. the optional GAP packages spkg would keep working
with Sage releases prior to Sage 3.3.
One way to attack this would be to use something along the lines of
mabsh...@sage:/scratch/mabshoff/sage-3.4.alpha1/spkg/standard$ ./
newest_version gap
gap-4.4.12.p1
and strip the ".pX" off the version number in case it exists. Another
one would be to look into the right directory and find the highest
currently installed GAP version.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
