|
|
Subscribe / Log in / New account

A new GCC runtime library license snag?

A new GCC runtime library license snag?

Posted Jul 29, 2009 8:05 UTC (Wed) by rsidd (subscriber, #2582)
In reply to: A new GCC runtime library license snag? by Baylink
Parent article: A new GCC runtime library license snag?

My understanding is that egcs forked because it was impossible to get changes into the FSF tree. Despite ESR's analogy of free software with "the bazaar", the FSF has always had a "cathedral" mode of development. The egcs people did desire eventual re-merging and were careful to assign copyrights to the FSF. Eventually when the FSF realised gcc 2.8 was a dead-end and egcs had leapfrogged it, they agreed to re-merge with egcs and call the result gcc 2.95. But this happened after most serious users had switched to egcs anyway: gcc 2.7.x was showing its age and gcc 2.8 was seriously flaky. So it was bowing to the inevitable, but it wasn't so bad for the FSF, since it was still GNU software with copyrights held by them. The current situation could turn out worse.


to post comments

A new GCC runtime library license snag?

Posted Aug 2, 2009 1:30 UTC (Sun) by landley (guest, #6789) [Link]

Actually, the FSF _was_ the "cathedral" in CATB, and Linux was the "Bazaar". (Eric's said so in a couple interviews over the years, he just didn't play it up in the paper itself so as not to set-off the FSF's supporters.) Eric was comparing different methods of open source development. (Keep in mind that CATB came out shortly before the egcs fork, when gcc development was stagnant.)

Eric got the idea for the paper at a conference in 1996, which is described in some detail here:

http://oreilly.com/openbook/freedom/ch11.html


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds