I'd rather see a link to the POSIX standard defining link as atomic.
IEEE Std 1003.1-2003
http://www.opengroup.org/onlinepubs/007904975/functions/link.html
The link() function shall atomically create a new link for
the existing file and the link count of the file shall be
There is one big question which must be answered first: will it have
to be Autoconf 2.13 compatible?
We use it for the PHP project (80k lines configure script),
because 2.5x is 5 to 6 times slower and contains a
dependency-ignorant cache system.
So, please don't create
I developed/maintain the configure script for ImageMagick. While the
total lines in the generated configure script is meaningless, it is
less than 1/2 of what you report for PHP, and PHP's configure script
is 4-8X larger than typical configure scripts for other large packages
(e.g. 4X
[Cc line trimmed]
me too! :)
I think we have heard all arguments by now. There is no need
to reiterate them.
Whatever the outcome of this thread might be -- I hope those
who work on libtool will continue to provide a toolkit which
is suitable for all of us --
I'm looking for information on the portability of find(1). Please,
send me everything you know. In particular, I think I'm understanding
that `{}' is portably replaced by the argument only when alone, i.e.,
exactly
'{}' can only be used portable, if it is a separate argument.
Also