Hey Basu, thanks! That sounds great.
Can you open a ticket to fix the developer guide with this information (the
last section on sagenb development)? (Suitably generic, of course.)
- kcrisman
On Tuesday, April 8, 2014 10:45:24 AM UTC-4, P Purkayastha wrote:
>
> There is an easy fix. The main reason why it has broken sagenb development
> is because "sagenb/sagenb/flask_version" is a symbolic link to
> "sagenb/flask_version" - I do not know why it is set up like this. So,
> doing the following will allow you to work on sagenb dev - I will assume
> that your sage is in ~/sage and sagenb is in ~/sagenb:
>
> $ cd ~/sagenb/sagenb
> $ rm flask_version
> $ mv ../flask_version .
> $ cd ~/sage/local/lib/python/site-packages/sagenb-0.10.8.2-py2.7.egg
> $ mv sagenb{,-0.10.8.2}
> $ ln -s ~/sagenb/sagenb .
>
>
> And now, you can continue to work on sagenb dev in ~/sagenb.
>
> - basu.
>
> On Tuesday, April 8, 2014 10:33:03 AM UTC+8, kcrisman wrote:
>>
>> With the new directory layout,
>> http://www.sagemath.org/doc/developer/sagenb/index.html no longer makes
>> any sense, and I don't see any easy way to do any sagenb development
>> without making new (s)pkgs. Is that correct? Any ideas for making this
>> simpler?
>>
>> Thanks,
>> - kcrisman
>>
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
