KDE/4.11 branched what to do with kde-workspace?

[Ben Cooksley]

Hi all,

Just a side note here: using any branch name other than 'frameworks'
for KF5 based development in kde-workspace will throw a wrench in the
tools which depend on the KDE dependency metadata file. This includes
the CI system and kdesrc-build as well to a certain extent.

Fixing this will require negation statements in the dependency
metadata file to strip kde-workspace of it's branch autosensing
dependencies and replace them with branch strict dependencies.
Dependencies which do not yet support Qt 5, or support Qt 5 with the
same branch cannot be supported using this method - as kdelibs master
will get dragged in.

If kdelibs master gets dragged in, then the build will fail (as
kdelibs master does not exist for Qt 5).

ie. You will not be able to depend on those projects which support
both Qt 5 and Qt 4 builds in the same branch, and which depend on
kdelibs. You will also be imposing a maintenance cost on the
dependencies metadata file.

Regards,
Ben

Note: the statements would look something like this:

kde/kde-workspace[master]: -kde/kdelibs
kde/kde-workspace[master]: kde/kdelibs[frameworks]
kde/kde-workspace[master]: -kde/kdepimlibs
kde/kde-workspace[master]: kde/kdepimlibs[frameworks]
kde/kde-workspace[master]: -kde/kdelibs/kactivities
kde/kde-workspace[master]: kde/kdelibs/kactivities[frameworks]
kde/kde-workspace[master]: -kde/kdelibs/nepomuk-core
kde/kde-workspace[master]: kde/kdelibs/nepomuk-core[frameworks]