Re: combined report for make check?

2013-01-22 Thread Karl Berry
With a non-recursive, top level Makefile. Quick example: So, replace a nicely separated source setup with munging together the information about everything in one place? Thanks for the suggestion, but that seems like a major step backwards in maintainability to me, so I'll decline. Life goe

Improving user experience for non-recursive builds

2013-01-22 Thread Stefano Lattarini
[+cc bug-automake, so that we won't forget about the issue] [future replies should drop the automake list] On 01/22/2013 02:22 AM, Miles Bader wrote: > Stefano Lattarini writes: >> The best solution is on the user-side IMHO: fix the build system to >> use less (ideally none) make recursion. Both

Re: combined report for make check?

2013-01-22 Thread Stefano Lattarini
On 01/22/2013 12:09 AM, Karl Berry wrote: > This would require to change the 'check-recursive' targets not to > share the same code with the other '*-recursive' targets. I really > don't want to go there. > > Totally reasonable :). > > The best solution is on the user-side IMHO: