On Jan 21, 10:50 pm, "Soroosh Yazdani" <[EMAIL PROTECTED]> wrote:
> Hi,
Hi Soroosh,
> there seems to be some exciting progress in making packages for sage.
> However, I'm curious if there is a plan for allowing normal users have their
> own sage libraries that they can edit. That is, if a normal user runs "sage
> -clone" on a sage that is globally installed, a copy of the cloned directory
> will be made in his home directory, and he can edit the appropriate files.
> And from then on, there is a hg branch that he will have access to.
>
> Any ideas how best this can be done? Right now, what I'm thinking of is
> having a sage directory in the user's directory the first time sage is ran,
> and a link to the devel/sage in there. Can that work?
Hmm, I think there is a problem when building the extensions since you
will need to have write permissions to copy the resulting dynamic
library over. That could be potentially avoided by having the Sage
python directory in there too, but I am not quite sure how much work
needs to be done to make that possible. But I agree that for a multi
user system with centrally installed Sage such a feature would be
great.
> Cheers,
> Soroosh
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
