OLPC are starting to look at F18.
Things look surpisingly good, but one thing we're missing at the
moment is a recent webkitgtk3 build.
This is https://bugzilla.redhat.com/show_bug.cgi?id=843428
I have a fix, but I can't test it since the tree is currently broken:
something pulls in source-highlight, but that package hasn't yet been
rebuilt for the new boost version.
If source-highlight-3.1.6-3.fc18 were to be built in koji, the problem
would be solved. However, this hasn't happened yet - after a few days
If someone could have a manual poke-around (if not doing so already)
that would be much appreciated.
I've picked up a Mele A1000 set top, which uses the Allwinner A10 CPU.
I don't see a Fedora port for this one yet, so I might take a shot at
it. But first I wanted to ask if anyone else has already started this?
The CPU is a Cortex A8, and there is an Ubuntu port, as well as its
native Android OS.
Ok so my quest for more reasonable build time comparisons is still going. I must be really bad at this... So I tried two new versions of the script, one which just took PA's longest buildarch time and SA's shortest buildarch time, however, the overall times summed up turned out to be way too favorable on our behalf. The latest version now sums up the buildarch times and divides them by how many of them there were. I think its a bit better because the faster builders with faster build times will pull up the slower build times, essentially its just an average calculation. The offset now for us looks like around 15 days (half a month slower)? Anyway, the page is the same. I still haven't filtered out our slowest builders from this list either so the number of days could probably go down if I did. Let me know if these numbers seem a bit more reasonable!
Thanks to Peter for pointing out that the previous times I had were overall task times and not actual buildarch times so I re-wrote my script to gather that data instead. Basically the script just adds/sums up the time it took for each arch so (i686 + x86_64) and (armv5 + armv7) and compares/totals them up. If indeed my numbers are correct this time, it looks like we took an extra 32 days or about a months worth to complete? Keep in mind these times also include our slowest builders, where in which if you assumed a build farm composed of only our biggest/best machines, it'd probably be a lot faster (Brendan was recommending I filter out the slow ones). You can verify the task times by clicking on the links in the page below: