|
From: | Paul Eggert |
Subject: | Re: master has switched from Automake to GNU Make |
Date: | Fri, 17 Mar 2017 14:33:44 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 03/17/2017 12:51 PM, Eli Zaretskii wrote:
How about something like this instead: You can now run './autogen.sh git' or './configure'.
That would add complexity to a process that is already overly complicated. Plus, at that point there are other plausible things to do (i.e., other than './autogen.sh git' and './configure'); why list just those two possibilities?
Better would be to have plain './autogen.sh' default './autogen.sh all' instead of to './autogen.sh autoconf', so that the trailing message would simply say:
You can now run './configure'.That way, developers ordinarily wouldn't need to worry about running './autogen.sh git'. The rare developers who prefer unusual Git settings could use './autogen.sh autoconf' instead of plain './autogen.sh', or they could run plain './autogen.sh' and then apply their preferred settings atop the standard settings.
[Prev in Thread] | Current Thread | [Next in Thread] |