Taher Shihadeh wrote: > Hello :) > > LinuxInsight wrote: >> Oh, I see... Somebody ought to buy some faster machines for those >> autobuilders, I mean it can't take THAT long to finish building a few >> small packages. > I wouldn't use the word 'few' here. Las time I checked, Debian unstable > had 30500 or so packages. Multiply that by the number of supported > architectures, and even autobuilding a small subset seems like an > impressive task to me ;-) >
Hey, computers are really fast nowadays. I update my unstable quite often and you know what, in last 24 hours there really wasn't that many new packages. And stable is slowly moving target anyway. So I'd guess there's ample CPU available to build cute new cherokee_i386.deb. I didn't even know autobuilders are doin' the work before Gunnar explained. I thought packages are still packed by a maintainer and uploaded. But, I'm sure that the autobuilder system has some shortfalls that could have been solved better. For example each and every time some of the package sets arrive in unstable, some of the packages are updated, but I have to wait day or two for the rest, sometimes even more. And it always looks the same, they always come broken in a predictable way. In many cases those are quite small packages. For example whenever I see new version of git has been prepared, EACH and EVERY time the proper thing to do is to immediately put all those new git packages on hold, one by one. Because the git-core package NEVER comes with them, and they ALL depend on it. 2 days later git-core comes, also quite predictable. ;) Now tell me that autobuilder always comes short just of git-core and manages to perfectly build everything else? Sorry if I'm not convinced... And apologies to the list for the off-topic rant. -- http://www.linuxinsight.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
