Re: [Automake-ng] [PATCH] [ng] maint: rename automake -> automake-ng, aclocal -> aclocal-ng

[Jim Meyering]

Stefano Lattarini wrote:
> On 04/15/2012 02:00 PM, Jim Meyering wrote:
>> Stefano Lattarini wrote:
>>> On 04/14/2012 08:35 PM, Jim Meyering wrote:
>> ...
>>>> Hi Stefano,
>>>>
>>>> Won't this cause trouble for those who want to use the new tools?
>>>>
>>> Yes, unless they create a couple of symlinks:
>>>
>>>   automake -> automake-ng
>>>   automake-0.5a -> automake-ng-0.5a
>>
>> If you change the names, is there still justification for the smaller
>> version number?
>>
> Yes; see below, at the end of my reply.
>
> But I'm less and less convinced that changing the names is a good move
> at this point -- too much churn to avoid such a small source of possible
> confusion...
>
> Moreover, the present patch shows that such a renaming can be done with
> little fuss and churn for what concerns the changes required to the
> automake source tree; so the patch can be easily resurrected at a later
> time, when (if ever) we feel that the renaming is truly warranted.
>
> So, I say we drop this change and this discussion for the moment.  OK?

Sure.  Thanks.

>> Alternatively, you could make it so automake (the ng version) stops 
>> immediately
>> unless there is an "ng" option in configure.ac's AM_INIT_AUTOMAKE(...) list?
>> Then, there is no risk of using automake-ng on a project that does not
>> explicitly request it, and there is no need to pollute autoreconf
>> with the "-ng" suffix.
>>
> This is a nice idea, easy to implement, and with little churn.  Will do.
> Thanks.

Glad you like it.