[kde-freebsd] Fix 4.10 ports?

[Tijl Coosemans]

On Sun, 27 Oct 2013 23:56:51 +0000 Schaich Alonso wrote:
> On Sun, 27 Oct 2013 23:39:30 +0200
> Raphael Kubo da Costa <rakuco at FreeBSD.org> wrote:
>> Tijl Coosemans <tijl at FreeBSD.org> writes:
>>> On Sat, 26 Oct 2013 23:53:24 +0300 Raphael Kubo da Costa wrote:
>>>> Tijl Coosemans <tijl at coosemans.org> writes:
>>>>> Is it worth spending time fixing KDE 4.10 ports for FreeBSD 10.0 or will
>>>>> KDE 4.11 hit the tree soon?
>>>> 
>>>> What kind of fixes do you have in mind?
>>>
>>> http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2013-10-24_13h53m31s/
>>> Search for "kde" under "Failed ports" and "Skipped ports".
>>> The kde meta port currently doesn't package because of failures in
>>> step-4.10.5_1, kdesdk-4.10.5 and kopete-4.10.5.
>> 
>> I've somewhat started ignoring the pkg-fallout errors for KDE ports
>> because a lot of them are just random segmentation faults in the build
>> process.

Those three at least are consistent failures and there are multiple PRs
about them.  But the random failures need to be fixed too.  With pkg more
people will start using packages especially for heavy packages like kde
and it's not good if kde or parts of it randomly disappear from the server.

>> In any case: if the failures are still present in 4.11.x (or git
>> master), I'd say it makes sense to fix the versions in ports as the
>> fixes are still valid for future versions. Otherwise (ie. it's a failure
>> only in 4.10.5) backporting the fixes should be easy.
> 
> I think area51 commit r9387 should be applyable to ports to fix the broken
> libmsn "dependency". kdesdk was split into smaller packages for 4.11 so
> there's no compatible patches. step fails with clang on area51. And last but
> not least marble (4.11.2) builds fine with either compiler but segfaults on
> invalid memory reads at startup.

My question was, will FreeBSD 10.0 ship with KDE 4.10 or with 4.11?
Do the 4.10 ports need to be fixed or not?