Shuttleworth: Not convinced by rolling releases

But it wouldn't be easy either.
Let's say KDE would release binary packages.
What should those contain, just the compiled source packages ?
Then where does the user get the other needed packages from, in compatible versions ?
Issues start already with libc. It's easy to get a dependency to a new version of libc, and then your binary does not start anymore on an older system.
Even more so with more exotic dependencies. For KDE this would be the required version of Qt, or those databases for nepomuk, etc.

KItware manages to release working binary packages at least of CMake by building those packages on a dedicated machine, which is kept at a software state several years old, so no new dependencies creep in, and additionally by linking most things statically into CMake, instead of using the system packages. But this goes against the Linux distro philosophy.

At least Slackware is a bit easier in this regard due to its superiour package system ;-)

Hmm...

Alex