#18256: Rebuild packages only if the version really changed
-------------------------------+------------------------
Reporter: rws | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.7
Component: build | Resolution:
Keywords: cythonize | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------+------------------------
Changes (by jdemeyer):
* component: cython => build
Old description:
> In #17851 cycache was necessarily disabled. This now leads to
> recythonizing everything when only the cython version **number was
> touched** (e.g. by checking out an old branch followed by merging
> develop). Ideally, cythonizing everything should only happen if the
> cython binary is different when compared to the last cythonizing.
New description:
I frequently checkout older branches to do a fix or a review. After
checkout I often merge develop. Now when I `make`, due to the change back
and forth in a package version, a full rebuild of that package is
triggered. But it is IMHO not necessary because I merged develop and so,
only some Python code really changed, or only specific `pyx` files. The
proposal here is to optimize the `make` behaviour in such cases.
--
Comment:
This has nothing to do with Cython, but with `make`.
--
Ticket URL: <http://trac.sagemath.org/ticket/18256#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
