Sage 7.0 on Mac

[Szabolcs Horvát]

I have two questions about Sage 7.0:

 - Will it be available on OS X?  Currently there seems to be downloads for 6.10 and 7.1beta2 but not 7.0.  The 7.1beta2 fails on startup.

 - Is there a list of major changes (other than the list of tickets closed)?  Does the bump in the major version from 6 to 7 signify big changes?  

[Dima Pasechnik]

I did try 7.1beta2 (non-app version) on OSX 10.11, it worked for me.
(note that once you started Sage for the 1st time, it cannot be moved to another location then).
What exactly does not work for you with 7.1beta2?

[Szabolcs Horvát]

I tried the app version. I copied it to /Applications, then I started
it. I get:

ERROR: The Sage installation tree has moved

from /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma
to /Applications/SageMath-7.1.beta2.app/Contents/Resources/sage

This was the very first time I stared it.

> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-support/Wg4AQfMJYYQ/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-support...@googlegroups.com.
> To post to this group, send email to sage-s...@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-support.
> For more options, visit https://groups.google.com/d/optout.

[Dima Pasechnik]

First, I get a different error when I try opening Sage.app:

“SageMath-7.1.beta2.app” can’t be opened because it is from an unidentified developer.

(OK, this is expected)

If I override this by holding Control while opening it, I still get an error; the browser pops up with message

The Sage server is currently starting. Please wait...

but then I get a pop-up with an error.

The log says:

Setting environment variables

/Users/dima/tmp/SageMath-7.1.beta2.app/Contents/Resources/start-sage.sh: line 43: spkg/bin/sage-env: No such file or directory

Warning: overwriting SAGE_ROOT environment variable:

Old SAGE_ROOT=/Users/dima/tmp/SageMath-7.1.beta2.app/Contents/Resources/sage/

New SAGE_ROOT=/Users/dima/tmp/SageMath-7.1.beta2.app/Contents/Resources/sage

Checking install location

ERROR:  The Sage installation tree has moved

from /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma

  to /Users/dima/tmp/SageMath-7.1.beta2.app/Contents/Resources/sage

This is not supported, and Sage will not work. To install Sage from a

binary package:

... etc...

Now, if in Sage app I go to Terminal Session menu and start Sage from there, 

I see the patching script running in terminal and then the Sage terminal session starting (and working)

Now, if I quit, and then start Sage.app again, everything works as it should.

I'd say this is not good enough for an average user...

Probably one should write (create, I imagine there are OSX tools for this) a custom installer

to do this automatically.

Dima

-------------------------------

[Dima Pasechnik]

On Monday, February 8, 2016 at 4:26:48 PM UTC, Szabolcs Horvát wrote:

I tried the app version.  I copied it to /Applications, then I started
it.  I get:

ERROR:  The Sage installation tree has moved

from /Users/buildslave-sage/slave/binary_pkg/build/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidma
  to /Applications/SageMath-7.1.beta2.app/Contents/Resources/sage

This was the very first time I stared it.

see my last message in the thread on how I  fix this.

Does this work for you, too? 

[Ivan Andrus]

I’m sorry I haven’t been keeping up with Sage development as much as I would like.  

The file src/mac-app/start-sage.sh could probably use a bit of love from someone.  I’m planning to get to it, hopefully soon, but it’s just a shell script largely unrelated to the rest of Sage.app, so changing it shouldn’t require any specific knowledge of the app.

Anyway, on line 27 I try to find the SAGE_ROOT variable, and I add a trailing slash.  Based on the errors this looks wrong.  In fact the entire idea of setting SAGE_ROOT seems misguided now.  I think I added it for two reasons.  First, so that the path could contain spaces, and second to avoid changing sage location repeatedly after the app moved. 

But, especially if someone creates an installer, we can probably just assert that there are no spaces in the path, in which case a lot of the script could be simplified.

-Ivan

[Volker Braun]

This is now #20033