<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;"><div><div class="im"><blockquote type="cite">
I'm working on the master config...<br>One thing it needs is the (domain name and) port number where buildbot's own http server will be visible. Default is 8010. I guess it just needs to be open to the WAN and that's it.<br>
</blockquote><div><br></div></div><div>I think 8010 and 10012 are not filtered on that network.</div></div></div></blockquote><div><br>cool<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="word-wrap: break-word;"><div><div class="im"><br><blockquote type="cite"> I couldn't yet find a way to schedule in an anarcon-like manner, but i'll keep digging.<br></blockquote><div><br></div></div><div>
That machine is up all the time, so regular cron is fine.</div></div></div></blockquote><div><br>it's about the uptime of slaves, and scheduling is handled by the buildbot master (internally). e.g. my box is up very irregularly, which a called a "latent slave" in buildbot world, and i'm yet to understand how to integrate it<br>
<a href="http://buildbot.net/buildbot/docs/current/Latent-Buildslaves.html">http://buildbot.net/buildbot/docs/current/Latent-Buildslaves.html</a><br><a href="http://www.codelord.net/2009/10/04/writing-a-buildbot-latent-build-slave/">http://www.codelord.net/2009/10/04/writing-a-buildbot-latent-build-slave/</a><br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;"><div><div class="im"><br><blockquote type="cite">
Then the build sources/targets: one will be vanilla, which is in git, right? Or can i find it in SVN too? Buildbot seems to handle SVN more easily than git. The other is pdextended, is it true that it cannot be fetched with a one-liner, but we still need to get the 0.42 core and GEM separately? It will be a bit cumbersome to do this with buildbot (especially when detecting changes).<br>
</blockquote><div><br></div></div></div><div><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div style="word-wrap: break-word;">
<span style="font-size: medium;">vanilla is in git. Pd-extended 0.42 can be fetched with a oneliner using svn, it is just that currently Gem is an svn:external. Oh wait, perhaps 'scripts' is still from trunk. I can fix that. I think the first thing that would be most valuable is setting up builds for individual libraries, so checking out from svn and building, so like</span></div>
<div style="word-wrap: break-word;"><span style="font-size: medium;"><br></span></div><div style="word-wrap: break-word;"><span style="font-size: medium;">svn co <a href="https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/windowing" target="_blank">https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/windowing</a></span></div>
<div style="word-wrap: break-word;"><span style="font-size: medium;">cd windowing</span></div><div style="word-wrap: break-word;"><span style="font-size: medium;">make</span></div><div style="word-wrap: break-word;"><span style="font-size: medium;">make install</span></div>
<div style="word-wrap: break-word;"><span style="font-size: medium;">make dist</span></div></span></div></div></blockquote><div><br>ok, i'll test with single libraries (once i'm there), and will work it out as far as making a complete pd-extended. you could tell me then which sources we actually want to build at the end (and, eventually, you could also tell me what commands to use to build each source tree.)<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div style="word-wrap: break-word;"><div><span style="border-collapse: separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;"><div style="word-wrap: break-word;">
<span style="font-size: medium;"><br></span></div><div style="word-wrap: break-word;"><span style="font-size: medium;">Can buildbot handle making debian packages? That would be nice. I think that could be a oneliner.</span></div>
<div style="word-wrap: break-word;"><span style="font-size: medium;"><br></span></div></span></div></div></blockquote><div><br>it can attend "make package" or packaging by shell command, but only RPM creation is built in :(<br>
<br>Andras<br>
</div></div>