>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
[...]
Tom> I agree that having install-strip work efficiently is important.
Tom> However I don't believe that it is more important than (1) getting 1.5
Tom> out in a timely way (though I don't believe this will derail it either
Tom> way), or (2) autoconf 2.13 support.
Although i initially suggested it, there is another
install-strip approach that we completly forgot: install
binaries using the system's install, and strip them afterward.
MAYBE_STRIP=:
install-binPROGRAMS: $(bin_PROGRAMS)
@$(NORMAL_INSTALL)
$(mkinstalldirs) $(DESTDIR)$(bindir)
@list='$(bin_PROGRAMS)'; for p in $$list; do \
if test -f $$p; then \
f=`echo $$p|sed 's/$(EXEEXT)$$//;$(transform);s/$$/$(EXEEXT)/'`; \
echo "$ (INSTALL_PROGRAM) $$p $(DESTDIR)$(bindir)/$$f"; \
$(INSTALL_PROGRAM) $$p $(DESTDIR)$(bindir)/$$f; \
$(MAYBE_STRIP) $(DESTDIR)$(bindir)/$$f
else :; fi; \
done
install-strip:
$(MAKE) $(AM_MAKEFLAGS) \
MAYBE_STRIP=`test -z '$(STRIP)' && echo strip || echo $(STRIP)` \
install
Maciej> Note that autoconf 2.13 isn't an issue anymore, I think.
Maciej> Version 2.50 is already released.
Tom> I disagree. I believe that uptake of 2.50 will be slow and so
Tom> continuing support for 2.13 is important.
Tom> However, beliefs are not intrinsically useful. Can we find a more
Tom> rational basis for making this decision?
A survey of all the GNU packages? (though it's out of topic
here, I would really be interested in knowing the proportion
of autoconfiscated packages use Automake).
--
Alexandre Duret-Lutz
