Re: moving $(mkdir_p) from automake to autoconf

[Ralf Wildenhues]

* Ralf Wildenhues wrote on Thu, May 11, 2006 at 03:38:31PM CEST:
> * Paul Eggert wrote on Thu, May 11, 2006 at 01:53:12AM CEST:
> 
> > Hmm, but I now see
> > that my version may cause clashes between AC_PROG_MKDIR_P and
> > AM_PROG_MKDIR_P.  I'll look into that now.  Perhaps AC_PROG_MKDIR_P
> > should set a new output variable MKDIR_P rather than Automake's
> > mkdir_p?
> 
> Yes, I think using MKDIR_P would be a good idea.
*snip*

Hmm.  OTOH with your patch AC_PROG_MKDIR_P requires an install-sh that
is new enough anyway, and `autoreconf -vif' will happily overwrite it
with an older copy from the installed Automake version..

Maybe we need a notion "this macro requires Automake >= 1.10, if you use
Automake", to be used inside AC_PROG_MKDIR_P.  Alternatively, we could
just document that usage of both Automake and AC_PROG_MKDIR_P requires
  AM_INIT_AUTOMAKE([1.10])

since after all, this macro is mostly designed for users not using
Automake (and maybe Automake just moving to use the Autoconf version
eventually).

Cheers,
Ralf