Re: moving $(mkdir_p) from automake to autoconf

2006-04-19 Thread Ralf Wildenhues
Hello, I'm still undecided with this. I see the benefit, but I see quite a few subtle issues with it as well. I'd like to see a more evolved patch before judging. * Bruno Haible wrote on Tue, Apr 18, 2006 at 02:43:42PM CEST: > > + @defmac AC_PROG_MKDIR_P > + @acindex{AC_PROG_MKDIR_P} > + @ov

Re: moving $(mkdir_p) from automake to autoconf

2006-04-19 Thread Paul Eggert
Stepan Kasal <[EMAIL PROTECTED]> writes: > I second this proposal. I think this could be added right now, even though > we are in a freeze. I tend to agree, since it's taken from Automake. Assuming my minor patch to Automake for leading "-" is accepted I'd like that change put into Autoconf as

Re: moving $(mkdir_p) from automake to autoconf

2006-04-18 Thread Stepan Kasal
Hello, On Tue, Apr 18, 2006 at 02:43:42PM +0200, Bruno Haible wrote: > Therefore I propose to move the AM_PROG_MKDIR_P that defines an @mkdir_p@ > variable to autoconf. The sooner, the better. I second this proposal. I think this could be added right now, even though we are in a freeze. I think

moving $(mkdir_p) from automake to autoconf

2006-04-18 Thread Bruno Haible
Automake now has a good way for creating installation directories: it is multiprocess-safe, and uses GNU mkdir on GNU and Linux platforms, while using the portable install-sh as a safe fallback. Basically every package that does not use automake and that wants to install _anything_ in public direc