Well, what you have to be aware of is that Devpaks have their share of problems. If you want to make a Devpak for a library that uses C++ functionality, you have to make sure your users have the right compiler. GCC breaks ABI (Application Binary Interface - the way in which Class names and inheritances are encoded) quite regularly lately. 32. isn't compatible with the later versions, 3.4 isn't compatible with the former verions, and now the 4.0 isn't compatible with the rest...
Sadly, there is no way (yet) in a DevPak to check what ABI is available on the host.
Moreover, C::B is a multi-compiler environment. So you have to take care that the devpaks can only be installed in GCC, because until now that's the only platform they are available for.
I foresee that there will be quite some enhancements to do.