Hey wait, does that mean that you're going to regularly provide nightly builds of qt-copy, kdelibs, kdebase-runtime and all that jazz? I mean, *that* qt-copy that takes awfully long to compile, needs a lots of hard disk space for source and object files, and that I would prefer not to build by myself at all?

If that is actually the case, you should probably decouple those base packages from the Amarok build (but still letting it depend on them) and provide qt-copy & Co. as a general service for devs who want to develop on the bleeding-edge KDE trunk but don't like to compile the base libraries for themselves.

Or you could position Neon as general nightly build program open for all of KDE's packages, and add more of those as (additional) nightly build maintainers join the party. Think of how that would enable a whole lot more programmers to develop widgets for the new plasma, or make sure their applications are in sync with the upcoming KDE version, or of course hack on Amarok like there is no tomorrow!

Ok, the latter is possible also with the current packages, and I guess the former two as well, but it would be nice to see a nightly KDE libs build that is not *only* dependent on Amarok's needs, should they differ for any unanticipated reason.