Hi Ian,
Ian Leitch wrote:
When emerge is called on the production server; if 'remote-build' is in FEATURES then the build server is notified to build package foo and all its deps for client ID 123. An optional priority can also be set for security updates etc.
When the package is ready on the build server, it'll need to notify the production server somehow. Having a daemon running on the production server would be the easiest option, but probably the worst. Other options could be: Monitor an NFS mount (is this possible?), check the build server every n minutes (with a what's-ready request) then download from NFS/web server.
would that build server be a gentoo.org machine or is it a private one? if it's a private one, why not simply use distcc?
i don't think we have the $$$$$$ for such a huge box, so it would be a kind of p2p, but then we have to problem of trust. how can we assure that no malware code is in the compiled code?
One requirement of this system is that the production server and build server will need to share the same portage tree.
another plus for distcc
greetings,
blubb
signature.asc
Description: OpenPGP digital signature
