Sponsored link
Vyatta –
Linux & Open Source
Alternative to Cisco –
Advanced Routing,
Firewall, VPN, QoS..
Free Download ->
| |||||||||||
The Future of XFree86 - like gcc v. egcs?The Future of XFree86 - like gcc v. egcs?Posted Mar 27, 2003 9:07 UTC (Thu) by tjasper (subscriber, #4310)Parent article: The Future of XFree86 Doesn't this sound a little similar to the gcc v. egcs issue that came about a few years ago. Since then, gcc has come on leaps and bounds with it's support for x86 based processors. Hopefully the same will happen to X development. Also, regarding the lack of commercial support for X development. Maybe Keith is right that the hurdles to get onto the core team are too high and hence the lack of commercial interest. Could it be that it's easier for developers to be influential in other projects, hence commercial funging to push for their own ends? Just my comments from a grateful user of all this free software.... Trevor Jasper
(Log in to post comments)
The Future of XFree86 - like gcc v. egcs? Posted Mar 27, 2003 9:08 UTC (Thu) by tjasper (subscriber, #4310) [Link] OOps, funging should read funding!...
The Future of XFree86 - like gcc v. egcs? Posted Mar 27, 2003 20:03 UTC (Thu) by hazelsct (subscriber, #3659) [Link] The analogy of gcc vs. egcs may be a good one, as far as assuaging fears of "duplicated effort". Egcs forked in order to bring a more bazaar-like development style to the project for bug fixes, optimization improvements, etc., but never strayed far from the original interface. As gcc continued its infrequent releases (like 2.8.1), egcs folded in the changes. Eventually, the gcc people saw the light, decided to adopt egcs as gcc, and everyone was happy.But a major difference is that everything egcs did was in the open, here it seems one person worked behind the scenes to start a fork, and also made very large changes to CVS without consulting anybody. He hasn't replied (AFAIK) to the charges of dishonesty (which is apparently backed up by the email record). The point of all this being, X forks are not necessarily bad, but at least to this outsider, Packard's way doesn't sound at all like the right way to do it.
|
|||||||||||