Alver wrote:
I assume the reason behind the question was: "will platforms that have CDE now benefit from the changes made by the open source community that manages it now".
The answer there would probably be "yes", since it's not GPL. But I'm not an expert in license law.
I believe that if HP, IBM, and others wanted to include any new work done by the open sourced CDE, that they may have to drop their own CDE codebase or re-license it to be compatible with the LGPL. The LGPL allows linking to the work as a library, but not as part of a derivative work that is proprietary. For example, the CDE code can be linked against by third-party programs written for CDE, like a CAD program written for Unix. However, that is linking rather than creating a derivative set of programs. Improvements made for the open source CDE project could probably not be used by the Unix vendors under current licensing arrangements, because that would result in a derivative proprietary work (which the LGPL protects against). That is my current understanding of the situation (I'm not a lawyer).
There are still many bugs in the current Linux build of open source CDE, and many rough edges. I think the first phase was just to get it up and working. Now they are starting to clean up the code base, basically resolving a few thousand compiler warnings (everything is compiled with
ANSI
and
pedantic
flags). Some things still don't work, though, and there are some bugs that need to be worked out. For example, the
dtexec
program can start using 100% of the CPU under certain conditions if desktop is running for a long time. Essentially, the code is still alpha quality on Linux.
I think there is some work under way to also get the CDE code working under the BSD's, and some interest as well from Solaris people. I hope that work can continue to clean everything up and work out the bugs and compatibility issues. There are also some security flaws that are documented, and will probably be fixed at some point.