Subject: automake: configure has mode 755
Package: automake
Version: 1:1.4-p4-1.1
Severity: normal
automake produces a configure file with mode 0775. (At least, when
the user's umask is the default of 002. Presumably it's modified
appropriately otherwise.)
This of course corresponds to the permission bits rwxrwxr-x. This is
obviously completely inappropriate, as the code produced by automake
is something that should never been seen by human eyes.
To pick one examples:
# The following way of writing the cache mishandles newlines in values,
{
(set) 2>&1 |
case `(ac_space='"'"' '"'"'; set | grep ac_space) 2>&1` in
*ac_space=\ *)
sed -n \
"s/'"'"'/'"'"'\\\\'"'"''"'"'/g;
s/^\\([_$ac_cr_alnum]*_cv_[_$ac_cr_alnum]*\\)=\\(.*\\)/\\1='"'"'\\2'"'"'/p"
;;
*)
sed -n \
"s/^\\([_$ac_cr_alnum]*_cv_[_$ac_cr_alnum]*\\)=\\(.*\\)/\\1=\\2/p"
;;
esac;
} >&5
Worse than Perl!
Please, spare users the pain of seeing this by making the output
default to mode 0111.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux toey 2.4.17 #32 Tue Feb 12 08:53:12 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages automake depends on:
ii autoconf 2.52-6 automatic configure script builder
ii autotools-dev 20020222.1 Update infrastructure for config.{
Subject: re: obfuscated output from automake/autoconf
Date: Mon, 15 Apr 2002 18:59:13 +1000 (EST)
"ha ha, only serious".
(The convolutions of automake/autoconf/libtool are pretty bad, but
they seem the best available solution for handling portability, or if
not the best then at least the standard.)
Regards,
--
Martin