caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@ozemail.com.au>
To: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
Cc: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>, caml-list@inria.fr
Subject: Re: [Caml-list] Re: Tcl/Tk and RH 9
Date: 11 Aug 2003 07:26:35 +1000	[thread overview]
Message-ID: <1060550794.6174.94.camel@localhost.localdomain> (raw)
In-Reply-To: <3F35A58E.3030804@quasar.ipa.nw.ru>

On Sun, 2003-08-10 at 11:53, Alexander V. Voinov wrote:

> I do not mean that this would turn me to like 
> Tcl/Tk, but this is the reality we face.

This is the reality we face:
-----------------------------------------------
[skaller@localhost] ~>python
Python 2.2.2 (#1, Feb 24 2003, 19:13:11)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import Tkinter
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
ImportError: No module named Tkinter
>>>
--------------------------------------------
This is a standard, out of the box install of RH9.
If, for example, Government departments buy a heap
of Linux boxes and install RH9, they won't get Tk
as part of the deal.

So it would be foolish to continue development of
products that use it if you want to be part of the
growing market of vendors of enterprise level packages
for Linux.

Redhat has swung soldily behind Gtk. To the point
Tk is no longer considered worth installing by default.
Enterprise software such as Open Office doesn't use it.
It is no longer part of the enterprise level users
software base.



-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2003-08-10 21:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-09  2:03 [Caml-list] version 7 beta typing change? skaller
2003-08-09 12:10 ` Jacques Garrigue
2003-08-09 16:15   ` skaller
2003-08-09 16:33   ` [Caml-list] Tcl/Tk and RH 9 skaller
2003-08-09 16:59     ` Matt Gushee
2003-08-10 15:57       ` Eray Ozkural
2003-08-10 20:18         ` skaller
2003-08-10  1:43     ` [Caml-list] " Jacques Garrigue
2003-08-10  1:53       ` Alexander V. Voinov
2003-08-10 21:26         ` skaller [this message]
2003-08-10 23:15           ` Eray Ozkural
2003-08-10 23:24             ` Eray Ozkural
2003-08-11  0:41             ` Matt Gushee
2003-08-11  1:20               ` Eray Ozkural
2003-08-11  2:02                 ` skaller
2003-08-11  8:38                   ` Sven Luther
2003-08-11  9:41                 ` Christoph Bauer
2003-08-10 20:15       ` skaller
2003-08-11  9:17         ` Christoph Bauer
2003-08-12  4:14           ` skaller
2003-08-10 22:11     ` [Caml-list] " Olivier Andrieu
2003-08-10 22:45       ` Matt Gushee
2003-08-10 23:16         ` Eray Ozkural
2003-08-11  1:33         ` skaller
2003-08-12  7:11 [Caml-list] " Jason Gibson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1060550794.6174.94.camel@localhost.localdomain \
    --to=skaller@ozemail.com.au \
    --cc=avv@quasar.ipa.nw.ru \
    --cc=caml-list@inria.fr \
    --cc=garrigue@kurims.kyoto-u.ac.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).