Several projects used config/ without any hand written file in it,
thanks to Automake's wonderful ability to ship the files all by
itself. But then, often, such projects, when just checked out, or
de-tar'ed by hand, don't have a config/. Et soudain, c'est
l'accident :
~/src/vampire % autoreconf
Akim Demaille <[EMAIL PROTECTED]> writes:
So, should automake -i make sure the directory exists and create it if
needed? Or that would be considered unsafe (a typo in the name, et
voil=E0, a nasty dir pollutes your codeshore).
perhaps only if --force is also specified, else signal error
>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
[...]
Akim> So, should automake -i make sure the directory exists and
Akim> create it if needed?
autopoint and libtoolize usually run before automake
and put things into this directory too. So if some tools has to
create the directory, I
>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
adl> [...]
Akim> So, should automake -i make sure the directory exists and
Akim> create it if needed?
adl> autopoint and libtoolize usually run before automake
adl> and put
On Sat, 2003-09-27 at 02:20, Alexandre Duret-Lutz wrote:
> adl> autopoint and libtoolize usually run before automake
> adl> and put things into this directory too. So if some tools has to
> adl> create the directory, I think it should be autopoint.
>
> Sorry, I meant "it should be autoreconf"
> On Sat, 2003-09-27 at 02:20, Alexandre Duret-Lutz wrote:
adl> autopoint and libtoolize usually run before automake
adl> and put things into this directory too. So if some tools has to
adl> create the directory, I think it should be autopoint.
>>
>> Sorry, I meant "it should be autoreconf
