From: "naruse (Yui NARUSE)" Date: 2013-06-18T10:20:30+09:00 Subject: [ruby-core:55537] [ruby-trunk - Feature #8539] Unbundle ext/tk Issue #8539 has been updated by naruse (Yui NARUSE). jonforums (Jon Forums) wrote: > A good idea if the new maintainer appreciates (and understands why great multi-platform support is strategic to Ruby the language) the fine cross-platform work Kou and the other Ruby-GNOME2 members do for the gtk2 gem by providing a self-contained mingw binary gem for MRI Windows users. > > But, how embarrassing for MRI if it's Tk GUI toolkit gem was kinda-sorta-not-really-multi-platform and only supported, say, Linux and OS X. As far as I understand, people can also use Ruby/Tk on Windows if they install Tcl/Tk for Windows. And on OS X (and Linux) people also need to install Tcl/Tk and X11. > Is the key issue bit rot (Tcl/Tk 8.6.0 released in 12/2012) in core, or something more strategic like continued interest in pushing as many extensions from core into gems? Once we had an idea that Ruby distribution should be all-in-one package for every basic use caeses as rosenfeld says in [ruby-core:55533]. But now we have rubygems and it is good for libraries which is on different timeline. Therefore we have such reactions. ---------------------------------------- Feature #8539: Unbundle ext/tk https://bugs.ruby-lang.org/issues/8539#change-40021 Author: naruse (Yui NARUSE) Status: Open Priority: Normal Assignee: Category: ext Target version: current: 2.1.0 How about unbundling ext/tk from Ruby repository? ext/tk is a bundled extension library for GUI programming with tk. It is introduced in 1999 and long maintained with CRuby itself. But nowadays its maintenance is not so active. Moreover ext/tk is not the de facto standard over Ruby GUI though it is bundled for 14 years. (maybe because tk is not de facto of GUI toolkit) GUI libraries for Ruby should compete in the wilds. So I propose unbundling ext/tk. It should be another repository for example on github and people should install it as gem. How do you think? -- http://bugs.ruby-lang.org/