[bug-notifications] [texinfo 0003613]: texi2dvi doesn't work with /bin/sh

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=3613 
====================================================================== 
Reported By:                pfelecan
Assigned To:                dam
====================================================================== 
Project:                    texinfo
Issue ID:                   3613
Category:                   regular use
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     confirmed
====================================================================== 
Date Submitted:             2009-04-03 13:14 CEST
Last Modified:              2010-02-18 18:58 CET
====================================================================== 
Summary:                    texi2dvi doesn't work with /bin/sh
Description: 
The texi2dvi script uses as its default command interpreter /bin/sh

A simple invocation on the attached texi source gives:

texi2dvi t.texi
/opt/csw/bin/texi2dvi: local: not found
/opt/csw/bin/texi2dvi: BSTINPUTS: not found

Using explicitely the Bash command interpreter works:

bash texi2dvi t.texi
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 file:line:error style messages enabled.
entering extended mode
(./t.texi (/opt/csw/share/texmf-dist/tex/texinfo/texinfo.tex
Loading texinfo [version 2005-01-30.17]: Basics, pdf, fonts, page
headings,
tables, conditionals, indexing, sectioning, toc, environments, defuns,
macros,
cross references, insertions,
(/opt/csw/share/texmf-dist/tex/generic/epsf/epsf.tex) localization,
and turning on texinfo input format.) (./t.aux) [-1] )
Output written on t.dvi (1 page, 228 bytes).
Transcript written on t.log.

This is probably a "linuxism" as:

/bin/sh --version
GNU bash, version 3.2.48(1)-release (i486-pc-linux-gnu)
Copyright (C) 2007 Free Software Foundation, Inc.

My suggestion is to patch all the shell scripts in your package and make
it depend on CSWbash

See the enclosed test case

====================================================================== 

---------------------------------------------------------------------- 
 (0007475) pfelecan (reporter) - 2010-02-18 18:58
 http://www.opencsw.org/mantis/view.php?id=3613#c7475 
---------------------------------------------------------------------- 
IMHO we should depend on our stuff at least for coherency reasons but also
for freshness.