This post originated from an RSS feed registered with Ruby Buzz
by Daniel Berger.
Original Post: I'm feeling the need for DamageControl
Feed Title: Testing 1,2,3...
Feed URL: http://djberg96.livejournal.com/data/rss
Feed Description: A blog on Ruby and other stuff.
After seeing Aslak's talk on DamageControl...nothing happened. I thought to myself, "Hm...interesting. But do I, a lowly developer who mostly works on small libraries, really need that?". My initial reaction was "no".
Today I changed my mind. At 11:49am, MST to be precise.
You see, even the simplest of my packages occasionally smacks into a platform issue. So, I go through this laborious process of making code changes on my Sun box, running the tests, committing changes, switching over to my Windows box, checking out the latest code base, running the tests *again*, making any Windows specific changes I need to, committing *again*, then switching back to the Sun box...
Well, you get the idea. It's worse for extensions.
I suspect (or at least hope) that I can use DamageControl to automate this process. I also hope to use it for packaging and deployment, because I'm getting very tired of doing the whole "create .zip/.gz/.bz2/.gem files, upload them to RubyForge, and update the RAA entry" routine.
I talked to Aslak a bit at RubyConf, and showed him how he can setup webrick as a Windows service, rather than spawning it in the foreground as he does now. So, I'll probably submit some code/patches to DC, or just recommend the ruby-services package.
Previous Topic
