Just to remind everywhat what our (the KDE4-Solaris team) purpose is, or at least re-state my understanding thereof after being away for over a month with other things:
- We are here to package KDE4 for Solaris with complete functionality - We are here to try to get KDE4 shipped officially by vendors There are other groups who also work on KDE4 on Solaris, such as the Belenix guys; those are different but not incompatible efforts. I would *hope* that the division roughly goes (and this is based on how things work in FreeBSD- land) that we (KDE4-Solaris) make sure it compiles at all and keep close to the upstream, integrating patches as quickly as we can. Then distro folk can work on the tight and useful intregration of KDE4 into the distro. This works in FreeBSD land with the kde-freebsd team and PC-BSD, for instance. In the Linux world, we have most of the core KDE team and all of those distro's doing customization and integration work. Those two goals drag in some other requirements or ancilliary goals: - For both S10 and Nevada, both amd64 and SPARC - 32-bit-only processors are not supported, although Ben works on them - Using Sun Studio 12 - GCC is definitely easier, but not officially supported by the vendor - Using SS12 does help improve the quality of the codebase - Complete functionality means dragging in all the dependencies - Packaging means producing SysV packages usable by pkg_add At this point in time we've got KDE 4.1.1 up and running, presumably for both amd64 and SPARC (I haven't heard any success stories out of SPARC-land and the U45 has been off). Everything patched up and packaged as needed, and KDE4 patches mostly pushed upstream. But: - Some of the dependencies are now quite dated - The means to build the packages is rather convoluted I'll post some next steps and plans later this afternoon. [ade]
