Re: [sage-devel] naive question on build process/patchbot

2014-05-20 Thread Robert Bradshaw
On Mon, May 5, 2014 at 7:47 AM, William Stein wst...@gmail.com wrote: On Mon, May 5, 2014 at 7:10 AM, Ralf Stephan gtrw...@gmail.com wrote: Hello, please bear with me and give me a hint why ... 1. isn't make just doing sage -b whenever nothing in lib/ is changed (or any suitable

Re: [sage-devel] naive question on build process/patchbot

2014-05-20 Thread Ralf Stephan
On Tue, May 20, 2014 at 4:51 PM, Robert Bradshaw rober...@math.washington.edu wrote: On Mon, May 5, 2014 at 7:10 AM, Ralf Stephan gtrw...@gmail.com wrote: 2. why does patchbot make and test twice per ticket, even with skip-base? It shouldn't, why are you seeing this? ​This must have been

[sage-devel] naive question on build process/patchbot

2014-05-05 Thread Ralf Stephan
Hello, please bear with me and give me a hint why ... 1. isn't make just doing sage -b whenever nothing in lib/ is changed (or any suitable definition of lib)? A counterexample would suffice. 2. why does patchbot make and test twice per ticket, even with skip-base? i.e., is it not

Re: [sage-devel] naive question on build process/patchbot

2014-05-05 Thread William Stein
On Mon, May 5, 2014 at 7:10 AM, Ralf Stephan gtrw...@gmail.com wrote: Hello, please bear with me and give me a hint why ... 1. isn't make just doing sage -b whenever nothing in lib/ is changed (or any suitable definition of lib)? A counterexample would suffice. 2. why does patchbot