On 2016-11-22 18:35, Robert Bradshaw wrote:
What I'm not following here is how this is not the correct behavior,
nor how hashes would help other than adding complexity (e.g. one must
store the hash of a.pxd inside b.c). Also, manually setting timestamps
would risk incorrect builds (remember the sage -ba days).
It is totally correct behaviour. I guess what other people want is a fix
for the following:
(0) Start from up-to-date and built Sage
(1) Checkout old branch
(2) Checkout/merge new branch
(3) Build Sage
In this situation, the diff between (0) and (2) is much smaller than the
diff between between (0) and (1) or between (1) and (2). But still,
everything in the diff between (0) and (1) and in the diff between (1)
and (2) will be rebuilt even if it's not in the diff between (0) and
(2). Hashes would help with this since the hashes of most files are
identical between (0) and (2) even if the timestamps are not.
--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
