----- Original Message -----
Maybe it's worth to ask them (or look at for example Mer builds)
the difference in build times.
A few statistics from build.meego.com
- using the OBS and building in
qemu. These are really just approximate numbers, built in different
times with probably a different load...
I took Qt as an example as it's a package I know.
build19 started "build qt.spec" at Sat Nov 5 02:09:33 UTC 2011.
build19 finished "build qt.spec" at Sat Nov 5 03:01:43 UTC 2011.
approx. 1 hour
build17 started "build qt.spec" at Fri Nov 4 23:33:24 UTC 2011.
build17 finished "build qt.spec" at Sat Nov 5 00:05:03 UTC 2011.
approx. half hour (1/2)
armv8el vs i586 factor of 2
build42 started "build qt.spec" at Thu May 12 08:49:50 UTC 2011.
build42 finished "build qt.spec" at Thu May 12 10:42:21 UTC 2011.
approx. 2 hours
build11 started "build qt.spec" at Thu May 12 08:49:48 UTC 2011.
build11 finished "build qt.spec" at Thu May 12 09:09:47 UTC 2011.
armv7el vs i586 factor of 4
------ Fedora ------
2012-02-20 14:31:51,510 - Mock Version: 1.1.18
2012-02-20 15:05:21,089 - State Changed: end
approx. half hour
2012-03-18 17:58:09,566 - Mock Version: 1.1.18
2012-03-19 04:53:07,593 - State Changed: end
better not calculating...
So probably using Qemu could speed it up quite a lot. Also OBS offers
quite a lot of flexibility to decouple arch builds, disable selected
archs etc. But I'm not sure about the processes for chain builds,
updates, how they make the builds consistent (if one arch fails)...
From package POV:
* the KDE stack would suffer a lot of slow
builds due to dependencies,
even now it can take half day to have all bootstrapped
* currently we omit all ARM patches available in upstreams as we don't
need them and we don't have a chance to test even the patch is needed :(
* for fixing bugs, we could always try to reach any ARM guy to help with
Maybe a distribution of PandaBoards/R-Pi for every FAS account holder could
help, any sponsor? :D
/me is going to order R-pi soon :)
> devel mailing list
devel mailing list