[kde-solaris] KDE 3.4.3 Patches and Upgrades

[Derek Konigsberg]

That all sounds very disconcerting, as a project like KDE should be striving 
to have a clean and *portable* code base.  (Whenever I have to "beat code 
into submission" to make it compile on Solaris, half the time I'm running 
into issues that only exist due to gcc's lax-ness anyways.)

As much as it might sound like an undesirable fork, I'd definitely be 
interested in having a Solaris compatable source tree that was kept in sync 
with the "we only care about Linux" tree.  (along with a source distribution 
that anyone could download/compile/package to their needs)

I'd even volunteer to host a repository for such a project, if that'll make 
things easier.  (I have a Solaris-based co-lo server that I'm always looking 
for more things to do with.)

-Derek

On Sunday 16 April 2006 12:05 pm, Stefan Teleman wrote:
> On Sunday 16 April 2006 08:55, Derek Konigsberg wrote:
> > Out of curiosity, are all these patches going to eventually
> > get rolled into the KDE code base itself?  I ask, because I find
> > myself much preferring to compile all my own stuff (and thus
> > avoiding a special set of dependency software for each big project
> > like this I install).  However, KDE doesn't compile "out of the
> > box" on Solaris anywhere near as easily as it used to. (these days
> > I give up after a while)
>
> I asked a few weeks ago if KDE Solaris could have a separate branch
> with the patched source code. Some thought it was a good idea, but it
> does not appear there's much interest in it, and it certainly does
> not look like it is going to happen.
>
> Quite frankly, many changes required for Sun Studio are changes which
> should be in trunk anyway, and are the same perpetual bugs i keep
> having to merge since 2003. For example strchr(3C) must return a
> const char*, and cannot return a char*, and so on. But it does not
> appear that others share the same opinion. ;-)
>
> --Stefan