Slackware Developer Not Happy With KDE5 Development
With KDE Frameworks 5 and the related new KDE components being under active development and no longer doing monolithic "Software Compilation" releases, the problem described by Hameleers is basically that packages in their early stages of new development are breaking dependencies and becoming dependent upon other KDE components that are only available in Git form. Eric wrote:
There have been a number of releases for the KDE Frameworks 5 and Plasma 5 (which depend on the Frameworks) in decoupled release schedules. To me it is clear that the developers are not (yet) ready for this. Their workflows appear to be such that they write code which depends on other modules’ code which only exists in a Git repository. With the old “Software Compilation” that was never an issue since all these sources would be released simultaneously. Nowadays we are facing independent release schedules and what is the (expected) result? Software starts breaking down because not all of the git code is being released at the time when the dependent code gets released.
Until the "KDE5" code is breaking less, Eric refuses to package the new KDE code for Slackware. "It is a freaking mess with updates, reverts and apologies all abound on the mailinglists. Get your act together! In emergency and disaster responce training, you’ll learn that it’s all about communication. IT is no different in software development. In the “bazaar” model, it is still required of people to coordinate the joint effort or else you’ll end up with a pile of loose sand instead of something solid and useful. Coordination is communication during, not after the events."
However, he is confident that everything will be ultimately resolved. "Knowing the KDE community, the future releases of the KDE 5 components will gradually reach mature levels again."
Eric's KDE comments can be read in full via his blog.
23 Comments
