Summary: | programs/xterm | ||
---|---|---|---|
Product: | xorg | Reporter: | Jim Gettys <jg> |
Component: | * Other | Assignee: | Kaleb KEITHLEY <kaleb> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | blocker | ||
Priority: | highest | CC: | mharris |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 213 |
Description
Jim Gettys
2004-02-25 10:26:02 UTC
xterm-184 is the latest-and-greatest available from T.E. Dickey's web site at http://invisible-island.net/xterm/xterm.html and that's what's in the xorg tree on the -CURRENT and -RELEASE-1 branches. We will definitely update when a new version is available. Xterm is ostensibly already modularized -- the invisible-island xterm sources come already autotooled and anyone who prefers a modularized xterm is free to use it right now if they so choose. Indeed. We use the modularized xterm in Fedora Core 1, Red Hat Enterprise Linux 3, and current development as well. One problem is that the monolithic tree does not have an option to say "BuildXterm NO". I have a patch to do just that however. That probably belongs in a different bug report though. oops, due to bugzilla auto-jumping to the next bug report, which is pretty retarded, I accidentally reopened this one. From the looks of it, 6.8.0 will be the final monolithic release, and the xterm that will be shipped in it, is whatever is in it right now, as we're over both freeze deadlines and now only major critical stop-ship bugs are going in. Since this is the final monolithic release, it doesn't make sense to import a newer xterm into CVS, if it wont ever get shipped in a new release. Closing "WONTFIX" as per above. People should use the modular xterm. We should contact Thomas Dickey and see if he'd like to set up xterm CVS on freedesktop.org for maintaining xterm perhaps. xterm was updated to patchlevel 196 from Thomas Dickey for the 6.8.0 release, which is the most current release on his website as well, so this is effectively fixed for 6.8.0. Bugzilla forced me to write a comment, so it is a useless comment. Changing status to "FIXED" |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.