[Automake-NG] Automake vs. Automake-NG (was: Re: [PATCH] build: support and require Automake-NG)

2012-08-21 Thread Stefano Lattarini
On 08/21/2012 12:20 PM, Paolo Bonzini wrote: Il 21/08/2012 12:10, Stefano Lattarini ha scritto: (AC_SUBST): Define AM_VARTYPOS_WHITELIST to LIBFFI_EXECUTABLE_LDFLAGS RELOC_LDFLAGS. This is required because Automake-NG is stricter than mainline Automake in its make runtime checks on possible

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Paolo Bonzini
Il 21/08/2012 14:44, Stefano Lattarini ha scritto: But there is an important difference: Automake-NG is *not* the next version of Automake, it is the Next Generation: it's not meant to be merged into the Automake code base, nor to supersede Automake, because the two projects have different

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Paolo Bonzini
Il 21/08/2012 16:32, Stefano Lattarini ha scritto: Bottom line is: we want to make it clear that Automake-NG is something different from Automake -- albeit mostly compatible, deliberately, and with very, very similar design and API; and that a transition between the two won't be seamless --

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Diego Elio Pettenò
On 21/08/2012 08:06, Paolo Bonzini wrote: Exactly. The -NG moniker would have made no sense. What could have made sense would have been a mapping like Yes that would have helped _a lot_. Another thing that would have helped would have been out-of-the-box support for multiple installed

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Stefano Lattarini
On 08/21/2012 05:02 PM, Paolo Bonzini wrote: Il 21/08/2012 16:32, Stefano Lattarini ha scritto: Bottom line is: we want to make it clear that Automake-NG is something different from Automake -- albeit mostly compatible, deliberately, and with very, very similar design and API; and that a

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Stefano Lattarini
On 08/21/2012 05:06 PM, Paolo Bonzini wrote: Il 21/08/2012 16:53, Diego Elio Pettenò ha scritto: do you think the transition would have been less painful (I really hope the answer is yes, of course). From a distribution point of view... it wouldn't have been any less painful. It would have

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Ralf Corsepius
On 08/21/2012 06:01 PM, Paolo Bonzini wrote: Ok. So the question I'd like you to ask yourself are: This needs to be done for each NG-NEWS items. It could improve the existing users of Automake, and reduce the size of NG-NEWS. Both of which are good things! And I've done that already

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Diego Elio Pettenò
On 21/08/2012 09:30, Ralf Corsepius wrote: In Fedora we already are pushing around package maintainers to pass appropriate options to configure to revert this change, because silent make rules are non-suitable for building distros in batch jobs. The same is true for Gentoo. In other words,

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Stefano Lattarini
On 08/21/2012 06:30 PM, Ralf Corsepius wrote: On 08/21/2012 06:01 PM, Paolo Bonzini wrote: Ok. So the question I'd like you to ask yourself are: This needs to be done for each NG-NEWS items. It could improve the existing users of Automake, and reduce the size of NG-NEWS. Both of which

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Stefano Lattarini
On 08/21/2012 06:01 PM, Paolo Bonzini wrote: Ok. So the question I'd like you to ask yourself are: * Why does it make sense to request manual declaration of 'SUFFIXES'? * Does it make sense to do so in Automake, too? And another question: * Alternatively, could Automake-NG suggest

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Bob Friesenhahn
On Tue, 21 Aug 2012, Stefano Lattarini wrote: Maybe we just need good PR and advertisment in this. The python developers has managed to make a 3.0 release incompatible with the 2.x series, because they've been very clear and vocal about the breakage, and have been for a long time. We might

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Stefano Lattarini
On 08/21/2012 07:36 PM, Bob Friesenhahn wrote: On Tue, 21 Aug 2012, Stefano Lattarini wrote: Maybe we just need good PR and advertisment in this. The python developers has managed to make a 3.0 release incompatible with the 2.x series, because they've been very clear and vocal about the

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Paolo Bonzini
Il 21/08/2012 19:14, Stefano Lattarini ha scritto: * warn for unknown *_XYZFLAGS variables I'm still unconvinced it would be a good idea to introduce this incompatibility in Automake just for the sake of simplifying transition to Automake-NG, sorry. * warn for treating _SOURCES entries

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Stefano Lattarini
On 08/21/2012 08:58 PM, Bob Friesenhahn wrote: On Tue, 21 Aug 2012, Stefano Lattarini wrote: Because all of us have forgotten to drop the 'CC:' to that list (where the discussion originated from) at a proper time :-( If it had been held only on the automake list then there would be less

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Stefano Lattarini
On 08/21/2012 08:51 PM, Paolo Bonzini wrote: Il 21/08/2012 19:14, Stefano Lattarini ha scritto: * warn for unknown *_XYZFLAGS variables I'm still unconvinced it would be a good idea to introduce this incompatibility in Automake just for the sake of simplifying transition to Automake-NG,

Re: [Automake-NG] Automake vs. Automake-NG

2012-08-21 Thread Paolo Bonzini
Il 21/08/2012 20:58, Bob Friesenhahn ha scritto: Because all of us have forgotten to drop the 'CC:' to that list (where the discussion originated from) at a proper time :-( If it had been held only on the automake list then there would be less harm to the free software world Which harm are