On 11/5/2011 12:40 PM, Gary V. Vaughan wrote:
By the end of this particular set, libtoolize will have moved from the kludgy sed based interrogation of configure.ac to probe the arguments to various important macros so that it can determine what files to copy and where... to the much more splendid and reliable M4 based tracing mechanism I originally wrote for bootstrap last year before adoption into gnulib stalled.
IIUC, in the past libtoolize *itself* has not had any dependency on m4. Granted, it wasn't much use without autoconf, which needed m4, so most users of libtoolize would have had m4 installed anyway. But this change will add a *direct* dependency on m4, right?
That's ok with me, as it makes no *real* difference, but it should be documented somewhere.
-- Chuck
