Bug 10130 - (Reletively) Ancient Version of TCL?...
Summary: (Reletively) Ancient Version of TCL?...
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: tcltk   
(Show other bugs)
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2000-03-12 08:51 UTC by Jay Freeman
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-03-18 21:09:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jay Freeman 2000-03-12 08:51:27 UTC
Was just reading a (slightly dated) article about all the new features
that were coming out in TCL 8.3 and did a double take on the version.
After all, the latest version I had seen being used was 8.0.5 on RawHide,
how could they possibly be working on 8.3 :).  To make a long story
slightly longer, I actually visited scriptics.com to make sure that that
wasn't a typo of some sorts, and lo and behold, 8.3.0 was not only
correct, but it has already been released as of February 10th...  Any
particular reason that 8.0.5 is still the version being included in

Comment 1 Jeff Johnson 2000-03-12 20:06:59 UTC
All the pieces necessary to build a complete tcltk-8.[23] package did not
exist in late November when we had to commit to what libraries were going
to be in the build system for Red Hat 6.2, hence the decision to remain with
tcl-8.0.5 in Red Hat 6.2.

The missing laggard is usually tclX, which appears to have been released
for tcl-8.2 as of 2/7/00 (time stamp on neosoft), which means that it's
almost time to attempt a tcltk-8.2 for Red Hat 7.0 (dunno yet about tcl-8.3).

Comment 2 Jeff Johnson 2000-03-18 21:09:59 UTC
Fixed in tcltk-8.2.3-36. I'll try for 8.3 as soon as some of the dust settles
(cough, cough :-)

Note You need to log in before you can comment on or make changes to this bug.