Dear GNU Hackers,
In quite a few guides I saw people suggest using the foreign autoconf
style to avoid having to create the required text files.
The goal of this email is to get more people to use the GNU style, so
the interface for understanding an autotools project becomes more
consistent agai
On 10/29/2014 02:37 AM, Arne Babenhauserheide (IMK) wrote:
> Dear GNU Hackers,
>
>
> In quite a few guides I saw people suggest using the foreign autoconf
> style to avoid having to create the required text files.
s/foreign autoconf/foreign automake/
Not necessary. Coreutils is an example proj
Hi Eric,
Am 29.10.2014 13:47, schrieb Eric Blake:
> On 10/29/2014 02:37 AM, Arne Babenhauserheide (IMK) wrote:
>> In quite a few guides I saw people suggest using the foreign autoconf
>> style to avoid having to create the required text files.
>
> s/foreign autoconf/foreign automake/
Ah, yes. I
On 10/29/2014 07:36 AM, Arne Babenhauserheide (IMK) wrote:
>>> If autotools did this automatically, the barrier for using GNU style in
>>> the autotools with a version tracking system would be much smaller: Just
>>> write README and NEWS.
>>
>> autoconf can't do this automatically, but gnulib can.
Am 29.10.2014 15:04, schrieb Eric Blake:
> On 10/29/2014 07:36 AM, Arne Babenhauserheide (IMK) wrote:
If autotools did this automatically, the barrier for using GNU style in
the autotools with a version tracking system would be much smaller: Just
write README and NEWS.
>>>
>>> autoco
