jacks oddities

Tue Jul 13 08:08:00 GMT 2004

>-- Original Message --

>> The idea is now to override the jacks call in jacks.exp like this:
>>>> - catch {exec ./jacks gcj} msg
>> + set tcl_version [info tclversion]
>> + catch {exec tclsh$tcl_version jacks gcj} msg
>>Correct me if I'm wrong (I don't know anything about Tcl/Tk),
>but isn't "tclsh" supposed to be a symlink to the correct
>version of the Tcl interpreter? So shouldn't the above be just:
>> - catch {exec ./jacks gcj} msg
> + catch {exec tclsh jacks gcj} msg

Yes, but I have also a box which does not have the symlink. So I want to
make it work there too:)
>>Does it also make sense to check "info tclversion" and
>complain if it is not at least 8.3?

That's also a point I'm working on. We should probably check and complain
loud.
>However, I think a better fix would be to submit the
>proper fix to the Jacks guys. (And while you're at it,
>perhaps an updated gcj.log as well for the current
>mainline - or not, as it is always in flux. :-/)

True, but the reaction time of the jacks maintainer seems to be slow. (According
to internal sources :)
So I work out first a fix which we could apply immediately.
>Don't say "only" - any monotonic reduction in Jacks
>XFAILs is highly welcome, at least as far as I am
>concerned.

Sure, but it's because of the below. I would even make noise about only
one XPASS.
>>If you meant w.r.t. your statement of "about 60 XPASSes",
>then I was just confirming your findings and putting
>in the exact figure. I am sorry if you thought I was pointing
>out an inaccuracy.

I meant regarding my previous statement of 60 xpasses, it's more a correction
on myself.
Andreas