> > > > I think it would be very useful to have very explicit instructions for > > how to create and stay on "develop" from upstream *using the sage -dev > > scripts*. I'll eventually figure it out but it's nice to have it within > > Sage, again. Unified context. > >
This is actually almost something we can add to the developer guide. What would be the precise steps for someone to follow who had never used Sage before, and compiled it somehow in a folder called Sage (whether by downloading tarball or using git)? In principle this should all be possible *without* using git - setting up "develop" and "master" etc. But I'm not 100% sure how to do that from scratch. $ cd Sage/ $ ./sage -dev "command that sets up master" $ ./sage -dev "command that sets up develop" $ And then one can follow these instructions, maybe. > 3. If a new development version of sage gets released then run > > $ sage -upgrade develop > $ git checkout develop # check out your local branch > $ git status # check if develop is up to date. If not.. > $ git rebase origin/develop # ... if not.. do this. > Also, I didn't see really clear instructions in this thread on how to use the cache thingie... I promise this is a useful discussion, because if we can add it to the developer guide we'll be in good shape. -- 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/groups/opt_out.
