On 2014-11-18 23:15, Andrew wrote:
That is, the manual states that the recommended route is to use sage -br
unless you are modifying packages.
The manual is technically correct but can easily be misinterpreted. The
problem is that switching branches often *does* modify packages.
In some cases (a package upgrade which isn't tied closely to the Sage
library), you can get away with "./sage -b" and not building the new
package, but for some package changes, you really need to run "make".
My workflow is:
1. checkout the relevant branch that I want to work on
2. run "make"
3. make edits (this can be done in parallel with 2)
4. run "./sage -br"
5. goto 3
--
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.
