KDE Applications 16.04.0 packages available for packagers

Michael Pyne mpyne at kde.org
Sun Apr 17 00:59:46 UTC 2016

On Sat, April 16, 2016 08:49:10 Ben Cooksley wrote:
> On Sat, Apr 16, 2016 at 3:20 AM, Eric Hameleers <alien at slackware.com> wrote:
> > I understand that the CI tools need to be able to resolve
> > interdependencies. So, why not use CI functionality to generate a global
> > dependency list and publish that? It would be an essential first stop for
> > everyone trying to compile KDE components.
> If you clone the repository kde-build-metadata from git.kde.org you
> will find in the tools folder a script called "list_dependencies".
> Once given a branch group (usually kf5-qt5, but for Qt 4 based
> software you'll want to use latest-qt4) and the name of the repository
> it can spit out the complete list of projects a given tarball /
> repository depends on.
> Additional work would be needed to sort this into a build order, but
> for those of you whose packaging systems just need to know what to
> depend on, that should be quite helpful I think.

Actually the list_dependencies tool spits out the dependencies in a 
satisfactory build order already. By default it outputs all dependencies 
recursively, but can be set to output only direct dependencies.

As far as version-specific dependencies, that's a good point... the dependency 
set is a moving target after all.

But a simple solution might be to simply tag kde-build-metadata along with the 
rest of KF5 and Plasma 5 when we do a release, as a way to baking in what we 
thought the dependencies were for each release.

 - Michael Pyne

More information about the release-team mailing list