Source: jimtcl
Version: 0.81+dfsg0-2
Severity: minor
Control: found -1 0.77+dfsg0-3
[Please do not Cc: me, for I’m “on the list,” so to say, and
I try to reserve my inbox for private communication only.
I’d have set up Mail-Followup-To:, but there doesn’t seem to
be a way to make it point to the report being filed.]
[Using Severity: minor chiefly due to the inclusion of the
README.* discrepancy in this report; feel free to clone and
address the issues separately.]
It’s customary for packages to be built for Debian with all
possible options enabled; or, alternatively, for there to be
separate ‘fully-featured’ and ‘low-footprint’ packages (such
as vim-nox vs. vim vs. vim-tiny; or exim4-daemon-heavy vs.
exim4-daemon-light; etc.)
Assuming there’d be no negative implications for Jim users
in Debian (such as openocd) in doing so, I request that ipv6
and math options are enabled for Debian Jim packages; which,
I presume, could be achieved by adding --ipv6 and --math to
the second dh_auto_configure invocation in debian/rules:
24
25 override_dh_auto_configure: autosetup/jimsh0.c
26 dh_auto_configure --builddirectory=static/
27 dh_auto_configure -- --shared
28
Currently both options are evidently disabled:
$ jimsh -e "socket -ipv6 stream.server 9999 "
ipv6 not supported
$ jimsh -e "expr { sin (1) } "
syntax error in expression: " sin (1) "
$
It’d be nice to have UTF-8 support enabled as well (--utf8),
but I’m less certain that it won’t interfere with current Jim
users in Debian.
$ jimsh -e 'string length "\u2012" '
3
$ tclsh8.6 <(printf %s\\n 'puts [ string length "\u2012" ] ')
1
$
Overall, I’d think that /also/ having Jim packages built with
the --full configure option (which is to say, with support
for sqlite3, zlib and others) could come handy to some of us.
So far as I can tell, it’d involve making separate jimsh-full,
libjim-full and libjim-full-dev packages, which seems somewhat
unreasonable.
That, however, reminds me that there’s currently a discrepancy
between the README.* files installed by the package and the
features actually enabled at build time. Namely, the jimsh
package includes the README.sqlite.gz and README.utf-8.gz
files, which correspond to features that are disabled and
unavailable to Debian jimsh package users. Conversely, the
package /does not/ include README.namespaces, despite the
respective feature being enabled (by default.) Hence I also
request that this discrepancy be rectified.
TIA.
--
FSF associate member #7257 http://am-1.org/~ivan/
