#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: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-------------------------------+------------------------
Old 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.
New description:
???
--
Comment (by jdemeyer):
Hmm no, that's not true. There is logic in `src/bin/sage-spkg` to not re-
build packages if you're installing the version which is already
installed.
--
Ticket URL: <http://trac.sagemath.org/ticket/18256#comment:9>
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.
