[Zlib-devel] zlib gzopen_w function added

[Török Edwin]

On 03/18/2012 08:18 PM, Mark Adler wrote:
> On Mar 17, 2012, at 10:59 PM, Vincent Torri wrote:
>> to avoid such problems, would it be possible to use buildbot ? Hence, using cross compilation, you can test the compilation on several platforms easily.
> 
> Vincent,
> 
> If you or someone else wants to start to set up such a thing, that would be awesome.  From my quick perusal, it would require access to a set of slave platforms on which builds can be done automatically.  That access implies some degree of trust -- I'm not sure how much, but I see no mention in the buildbot stuff of protection against malicious intent.  For this to benefit zlib,
> access to remote buildbot slaves would have to be volunteered.

The buildbot can tell the slave to build anything, which includes running programs during the build process, so yes I wouldn't trust
a random buildbot master with my slave.
Usually the slaves should be run with various ulimit settings just in case something goes wrong, but that is no protection against malicious intent.

>  Is this what is done for other uses of buildbot?  Or is it normally used with a bunch of local machines in a controlled environment?

For ClamAV we run buildbot slaves on:
 - a set of machines we own
 - a set of machines where open-source projects can get access granted:
    - GCC Compile Farm
    - OpenCSW.org

We also have a build-script that people can run daily and FTP the results to a central server,
in case they want to volunteer some CPU cycles for a platform we don't have, but they are not confortable running buildbot on it.

Best regards,
--Edwin