View Single Post
Posts: 355 | Thanked: 566 times | Joined on Nov 2009 @ Redstone Canyon, Colorado
#15
Originally Posted by jolouis View Post
However in the mean time the argument to say "the autobuilder is preventing more applications" is in my mind not accurate at all. Okay, so let's say worst case scenario your app takes 2 days to build in autobuilder... If that's your product release/app release, then 2 extra days for people to wait doesn't exactly mean "there are less apps available because of it". Sure things get backed up a bit, but you're still talking about final releases here. I think the bigger problem is that many people are using autobuilder as their "testing compiler" instead of compiling locally.
Well mine compiled locally fine in the /scratchbox (I was building asterisk, fwiw) but didn't build in the autobuilder. There are always subtleties and the autobuilder is not identical to the scratchbox. Take a look here and you can see how many FAILS or other errors there are:

https://garage.maemo.org/pipermail/e...er/thread.html

I bet you *all* of those devs built their packages locally, to be honest.

It also does hold things up for more than just two days because you lose momentum. If it took 15 minutes to find out your build failed, you continue on with the project; if it takes you a couple days, well, you've lost all that mindspace and by then 50 other things have come flying at you to work on. It's not just two days wait, it disturbs a clean workflow. I've decided to not bother packaging on there until things get sorted out because it's agonizing to wait, heh.

That and the fact that you can't see any live build logs (like fedora does, for example), so there's no real way to know what state your package is in either.

Anyway, more boxes is obviously going to help. Hopefully they're huge.

-Jeff
 

The Following User Says Thank You to jebba For This Useful Post: