> If they hit continue, does Sage work as expected?
>

As far as I can tell, yes. The permissions of DOT_SAGE and the notebook are 
initialized and the user is asked for a password.
 

> This was implemented in http://trac.sagemath.org/ticket/15732 because 
>> Sage needs to write to some files in .sage, I believe.  So it is really 
>> raising a better error message than before, but I don't think Sage will 
>> work if they do not have write permission *somewhere*.  Someone can 
>> elaborate if that is not quite correct.
>>
>
> They do have access in their own home directory, under ~/.sage, but not in 
> /Applications/Sage.app.
>
>
> But currently Sage checks if it has moved since last time it was run and 
> writes a file somewhere with the path.  So I think you would have to run it 
> at least once as root for that to work.  
>
> The check I added to the app was to prevent it from running on a disk 
> image which has no hope of working.  My check merely checks if the sage 
> binary is writable, so I could perhaps improve it to allow installation by 
> root.  But I’m not entirely sure how to ensure that things will work (I 
> can't test things right now).  
>
> Can I just run `sage -c 1+2` and see if it succeeds?
>

I first go to /Applications/Sage.app/Contents/Resources/sage and this is 
what I get :

imac11:sage jerome$ ./sage -c 1+1

imac11:sage jerome$ ./sage

┌────────────────────────────────────────────────────────────────────┐

│ Sage Version 6.4.1, Release Date: 2014-11-23                       │

│ Type "notebook()" for the browser-based notebook interface.        │

│ Type "help()" for help.                                            │

└────────────────────────────────────────────────────────────────────┘

sage: 1+1

2

sage: quit

Exiting Sage (CPU time 0m0.02s, Wall time 0m3.68s).

imac11:sage jerome$ 

 

>
> Perhaps a setting in the Info.plist would allow the administrator to turn 
> off the check once they know things will work.  
>
> Any other suggestions?
>

That would be fine with me. If I could remove the password initialization 
(or randomize it) it would be even better since the machines are not 
accessible externally.
 

>
> -Ivan
>

Thank you,

Jerome Tremblay
LaCIM, UQAM 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to