[sage-devel] Re: recompilation with "sage -clone" and after "sage -sync-build"

2013-06-02 Thread Travis Scrimshaw
Hey, Could we at least get the hacked sage-sync-build into 5.10? The combinat queue has a few patch which create new cython files that replace python files (i.e. cythonizes them) which requires the sync-build to be run when people are moving ahead of those patches. Rebuilding all cython files

[sage-devel] Re: recompilation with "sage -clone" and after "sage -sync-build"

2013-06-02 Thread leif
leif wrote: leif wrote: 4) Minimally adapt sage-sync-build.py to reflect the (hard-coded) change by #14570. [May be easy as well, but potentially unsafe.] Even that turns out to be non-trivial, AFAICS, i.e., the whole strategy would have to get changed, as opposed to just some file / director

[sage-devel] Re: recompilation with "sage -clone" and after "sage -sync-build"

2013-06-01 Thread leif
leif wrote: leif wrote: John H Palmieri wrote: Is there a ticket for the sage-sync-build problem? Not yet. There are a couple of ways to (quickly or temporarily) "fix" this: 1) Unmerge #14570, which doesn't fix a bug, but only introduces a new (btw. non-configurable) feature. [A bit odd, e