[haiku-commits] Re: haiku: hrev46863 - headers/private/kernel/arch/arm
- From: "Adrien Destugues" <pulkomandy@xxxxxxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Fri, 14 Feb 2014 15:34:12 +0000
>> This is all sounding like WebKit on a micro scale. We didn't make any
>> commits for a year and they
>> removed all of the Haiku code (not because it caused them any extra work..
>> Just because it was
>> "unmaintained.. But working")... Setting back development quite a bit.
They asked on their ML if someone was taking care of it, and no one did. At
that point, there wasn't any change to it from us for a year, and what they had
upstream was certainly not compiling (try it yourself, a non updated webkit
port will break at least once per month because they have no stable APIs
between the platform-specific and common parts).
So yes, the #if HAIKU all over the place in common code, extra build files, and
lack of testsuites did cause them some extra work. WebKit would be fine with
having our port upstream, but not until we use a standard buildsystem (done,
this makes updating the port much easier as you don't have to update jamfiles
anymore, the CMakeLists are shared with othere ports) and set up a build bot,
so they can at least know when they break things.
Same for all these unfinished ports in our: you can't expect them to keep
working if there are no tests. we do have buildbots, but there has never been a
single succesful build there. The PPC port was broken by the introduction of a
mandatory ICU package, they were all broken by PM, and again by Scheduler (and
a few other changes in between). If you take these ports seriously, get at
least the buildbots to build something, so we can at least know why and when
they break.
--
Adrien.
Other related posts:
