Fri, 05 Aug 2005

Late last night I’d despaired of doing anything useful, particularly on tinderbox, which is a bit of a mess, and which had no short-term prospects of getting a central data repository a-la fluendo’s build bot. So I tried to go to sleep, at about 3am.

While laying in bed, I realized that if the extant patch for rss generation in tinderbox could be made to work, it would be easy enough to set up a planet tinder that could fake a respectable multi-machine/platform tinderbox, for minimal work. So I woke up.

10 hours later, I’ve submitted a patch to get rudimentary atom support in jhbuild tinderbox (should be easy for someone to improve the quality of the outputted data, I’m just wiped ATM), and I’ve also cleaned up the microtinder scripts to make them easier to use. To run a tinderbox right now should be basically 4 steps:

  1. ‘cvs co microtinder’ somewhere with several gigs of disk space. (Your exact mileage may vary.)
  2. ./
  3. ./[1]
  4. put the resulting ‘web-output’ directory somewhere public, either by symlinking to it on a public-facing box, or by putting an scp statement in the script somewhere.

Bam. Do that, you’ve got a tinderbox.

There are a couple details that may have changed overnight- the atom bits probably don’t work quite right, even with my jhbuild patch applied, so don’t send me atom feeds quite yet. There isn’t a planet for them yet anyway. But otherwise, if you’ve got a solaris box, or some obscure processor, or whatever, it is that easy- you can help get GNOME up and running on your box, and keep it that way, with no need to give Uncle Louie root :)

Anyway, having accomplished that, now I sleep…

[1] This step runs jhbuild, so of course you will likely have to install some dependencies, etc. If you’re experienced in setting up jhbuild, this should be trivial; if not, I recommend consulting the excellent and comprehensive guide to jhbuild dependencies from the wiki.