== Quote from bioinfornatics ([email protected])'s article > yes, > is not against you work, it is as a packager point of view. > while gdc will be not a gcc project, gdc can not be go in fedora.
That's not how I understand it. Fedora ships GCC-4.5 (not 4.4), and will shortly switch to 4.6. That is why it won't go in fedora. > and gdc do not follow gcc stable version because is not a gcc project .... Not really. I am a packager too (I maintain gdc in Debian and Ubuntu), and so far I've been updating the GCC versions in cadence with the Ubuntu and Debian releases. Natty will default to GCC-4.5, while the next Debian release will be based on 4.6, so there is no urgent need for me to port to 4.5 just yet. But depending on how quick FE merging goes, it could be that by February/April will be updated to the current trunk. If anyone wants to speed up the process, you know where to get the sources and submit patches. :~) > Same as said et start of this thread is not against your nice job. > I know for gdc becomme a gcc project gdc team need give is right. > But if you want really support gcc, you will need become a gcc project ... > why wait And what if license becomes an issue? As far as I'm aware, all authors need to have signed copyright assignment papers to donate gdc to the gcc project. It may turn out that parts of GDC would probably need to be rewritten using a chinese wall strategy (ie: so anyone who has seen the source code that is so licensed should not be allowed to work on the implementation of the replacement) if one such author refuses to sign. And I'd dread to think about needing to clean-up the some 25,000 lines of code that's maintained ( and that doesn't include Phobos or the DMDFE :) Regards
