On Sun, Mar 1, 2009 at 8:37 AM, mabshoff <[email protected]> wrote: > >
.... >> >> > 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. >> ... > > No, see my comments earlier in this thread, i.e. do *not* hard code > the GAP release since this will break the spkg on Sage releases > earlier then 3.3 and also next time GAP is updated. > Okay, but won't having a script which earlier than 3.3 versions can't find also break such an install? I guess I'm not completely understanding your idea and how I can help gap_packages* by implementing it. > > Cheers, > > Michael > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
