I just released a new Dstat. I finally spend some time doing the boring release-dance:
- Verifying all changes since 0.6.7
- Backporting changes to python 1.5 version
- Creating the release archive without all pending patches and experimental stuff
- Verifying ChangeLog and documentation
- Testing on all Red Hat and CentOS/RHEL versions
I am planning to do an mrepo 0.8.5 release very soon. For those new to mrepo, mrepo is a python tool that can download RPMs from repositories, but also from Red Hat Network and Yast Online Update (or CentOS or OpenSUSE for that matter), mount ISO images if needed, and create repositories out of it.
For the people that have heard of Red Hat Satellite, consider it a (free) light version that only covers downloading the updates and making it available.
I am a bit disappointed that I did not have access to it before doing the same presentation at 3 different other venues, as I could have learned much from it. It shows that I had not slept that night because of the stress and sleepless nights turn me hyperactive :-)
I was surprised of the enthusiasm and feedback I got during and after my Dstat presentation at FOSDEM 2008. Even though I revisited my older slides and made the presentation shorter, I was not as prepared as I was with previous presentations but apparently that did not affect audience participation :-)
mrepo works with helper-tools for the actual downloading of updates or creation of metadata and so the real meat is inside the tool called youget.
The aim of doing a set of Dstat presentations was not just to promote Dstat, but also to hear people's impressions and ideas. And lots of ideas were shared and ended up in the TODO list.
But one of the questions that I did not quite understand initially, turned out to be an interesting and useful idea. And after the presentation we sat together to show how simple it was to bring an idea into practice.