...ah, and to emphasize: in the old system, this simply wouldn't have happened. I would have applied the patch, and only the things that needed recompilation would have recompiled. Sometimes, as in this case, that would be an empty set. In the old days, I only recompiled Sage when I completely juiced my system... which wasn't an empty set, but it wasn't of large cardinality, either.
Basically, would it be possible to add an intermediate step where people could download only the relevant patch (like before), apply & experiment only with the patch (like before), & then, when that seemed okay, check against the most recent branch (like now)? Sorry if this sounds like ignorant babble; I'm not familiar with the correct vocabulary. john perry On Sunday, November 16, 2014 7:53:43 PM UTC+1, john_perry_usm wrote: > > On Sunday, November 16, 2014 5:52:16 AM UTC+1, Nathann Cohen wrote: > >> Hello everybody ! >> >> ... >> Just wondered if we could not have some "git hook" (I do not exactly >> know what it can do) to make sure that one cannot checkout a branch >> which is not a descendent of the latest release of Sage in the local >> history. >> > > Thanks for paying attention to that. :-) > > If I understand correctly, your proposals fix the problem with tickets, > but I think there's a bigger problem. Or, maybe I just don't understand, > but if so, you can correct me here, and that should save me trouble later, > right? > > In the most recent debacle that constitutes my attempts to help with Sage > ;-) I followed the steps listed in the developer's guidelines from the most > recent release: checked out a branch (apparently it checks out itself, > though I'm not sure) then modified the few lines of Python code, then > executed ./sage -br. Cue the complete rebuild of Sage. (This may be because > I downloaded a binary, but I don't think so. Even if so, it doesn't make > sense: I only changed a few lines a Python code.) > > *After* that, Travis Scrimshaw made some very helpful changes, but he did > them based on the development version. So, when I tried to work with it, so > as to give it a positive review (which actually needed more work)... cue > another complete rebuild of Sage. > > I don't see how the proposed change would have fixed either problem. Sorry > if this is completely off base, but I thought the extra clarification might > help. > > john perry > -- 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.
