--===============0351598195==
Content-Type: multipart/alternative; boundary="00000000000065a0580572db975b"
--00000000000065a0580572db975b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
I'd like to point out that not a single actual issue has been raised that
shows any issue with the current Tk gem.
Oh dear. I think you may be referring to a post that *I* made.
The best I've seen is an attempt at "gem install tk" that failed - not a
single line of error - nor any attempt to ascertain what the error was -
nor any mention of whether or not Tk was even installed on said machine.
In my earlier post, I did include (I will admit) a quite abbreviated
error message. If you really want the whole, rather long, output I
*can* include it, but the most salient lines are:
Warning:: cannot find Tcl library. tcltklib will not be compiled (tcltklib is disabled on your Ruby. That is, Ruby/Tk will not work). Please check configure options.
--8<---------------cut here---------------start------------->8---
Can't find proper Tcl/Tk libraries. So, can't make tcltklib.so which is required by Ruby/Tk.
If you have Tcl/Tk libraries on your environment, you may be able to use them with configure options (see ext/tk/README.tcltklib).
At present, Tcl/Tk8.6 is not supported. Although you can try to use Tcl/Tk8.6 with configure options, it will not work correctly. I recommend you to use Tcl/Tk8.5 or 8.4.
--8<---------------cut here---------------end--------------->8---
Looking at the log
/usr/local/lib/ruby/gems/2.4/extensions/amd64-freebsd-10/2.4/tk-0.2.0/mkmf.logI
see the following:
--8<---------------cut here---------------start------------->8---
"cc -o conftest -I/usr/local/include/ruby-2.4//amd64-freebsd10 -I/usr/local/include/ruby-2.4//ruby/backward -I/usr/local/include/ruby-2.4/ -I. -I/usr/local/include -I/usr/local/include -I/usr/local/include -I/usr/local -I/usr/local/include -isystem /usr/local/include -O2 -pipe -fstack-protector -isystem /usr/local/include -fno-strict-aliasing -fPIC conftest.c -L. -L/usr/local/lib -L/usr/local/lib -L. -fstack-protector -rdynamic -lX11 -lm -lruby24 -L/usr/local/lib -ltcl86 -lX11 -lm -lunwind -lexecinfo -lprocstat -lthr -lcrypt -lm -lpthread -L/usr/local/lib -L/usr/local/lib -lc"
conftest.c:3:10: fatal error: 'tcl.h' file not found
#include <tcl.h>
--8<---------------cut here---------------end--------------->8---
So, *is* there a tcl.h installed? Of course there is:
# find /usr/local -name tcl.h
/usr/local/include/tcl8.6/generic/tcl.h
/usr/local/include/tcl8.6/tcl.h
But of course, this is the *current* version, not an obsolete version.
Ruby Tk most certainly, at least under conditions that I can validate,
works under Tk 8.6.8 - from a fresh linux system I installed Ruby - Tk -
and then gem install tk worked without issue.
I don't run any version of Linux for production work.
I make no assertions other than any statement that "Ruby Tk relies on an
outdated version of Tk" is not correct. That does not imply nor assert that
the installation process is smooth - easy - or anything else (although in
my scenario it certainly was anything but painful).
Absent actual bug reports of issues that stem from someone at least
attempting to read the instructions provided in the repo[1] then I think it
is rather rude to call a project dead or whatever other terms have been
used over the last few days. Claiming that people are not nice while
trashing the work of others as not working seems rather counter productive.
First of all, I don't think that I *ever* claimed that people are not
nice, nor have I *trashed* the work of others. Claiming that the
current state of affairs is not working is not "trashing" the work that
has already gone into this, but it stating the fact that that work has
(as far as I can see) stopped.
I (like I imagine most people) rely on the what is it packaged for
one's own particular platform. I have no desire (like I imagine most
people) to debug problems for a package that I don't actually use
(though I might use if I had some reasonable assurance that it would
actually work).
It is great to be passionate about something - but one needs to temper
passion with respect for those that actually do the work - nothing is
gained by typing "gem install tk" having it not work and then claiming the
project is dead because of that.
If I have given the impression that I do not respect the work that
other people have devoted to it, the I *do* apologise. I do not want
to denigrate the efforts of others, but only to express my frustration
that the state of GUI support is now so poor in Ruby.
···
On Tuesday, 7 Aug 2018 1:18 PM -0400, John W Higgins wrote:
--
Will
