After having some last minute problems with both the build system and the licensing, I finally released ccbuild 2.0.0. Bring on the issues! Reasons to expect issues to pop up are multi-threading support using OpenMP and using a single top-level o directory, instead of one per directory. Any command depending on the directory structure (like makefile).
Apart from those changes, this new release is moving away from SourceForge.net. After spending about 30 minutes trying to find a button to change the default download (which pointed to an old release), I decided to give up on the weird collection of hosted apps and commercials that SourceForge hosts. I've now settled for github.com. These are the things I missed at SourceForge and love at github:
- The default bugtracker just works and integrates into the development back-end (listens to my commits)
- Developer centered, it makes it easy for me to work with instead of giving me a large collection of partially working things I need to integrate myself.
I've also decided to just host my own website, the new home is: http://logfish.net/pr/ccbuild/ which now also includes the file releases. This means that I won't be able to use the SourceForge CDN, but no worries, with the power of metalinks I decided to do my own scalable CDN using dynmirror.net.
Debian packages are going to appear in my PPA first, but will hopefully enter the universe soon after that.