libtoolize: no need for umask 0 now that copying does not use tar.

The umask calls seem to be left over as a workaround for several
releases ago when libtoolize copied libltdl sources with the help
of tar.  Now that we use cp or ln -s exclusively, this just
needlessly makes the files world writable; we should just respect
the users' own umask setting.
* libtoolize.in (func_copy): Remove umask 0 calls and simplify.

Signed-off-by: Gary V. Vaughan <gary@gnu.org>
This commit is contained in:
Tijl Coosemans 2014-11-28 16:46:56 +00:00 committed by Gary V. Vaughan
parent 16bcf18849
commit cbeefbc8f0

View File

@ -392,11 +392,7 @@ func_copy ()
# Filters always take priority.
if test -n "$my_filter"; then
if $opt_dry_run || {
( umask 0
$SED -e "$my_filter" "$my_srcfile" > "$my_destfile"
) >/dev/null 2>&1
}
if $opt_dry_run || $SED -e "$my_filter" "$my_srcfile" > "$my_destfile" 2>/dev/null
then
func_notquiet_once "$my_msg_var"
if $opt_verbose; then
@ -422,11 +418,7 @@ func_copy ()
my_copy_msg="$my_copy_type file '$my_destfile'"
$opt_verbose && my_copy_msg="$my_copycmd $my_srcfile $my_destdir"
if $opt_dry_run || {
( umask 0
$my_copycmd "$my_srcfile" "$my_destfile"
) >/dev/null 2>&1
}
if $opt_dry_run || $my_copycmd "$my_srcfile" "$my_destfile" 2>/dev/null
then
func_notquiet_hdr "$my_msg_var" "$my_copy_msg"
else