CI Requirements - Lessons Not Learnt?
kevin.kofler at chello.at
Fri Jan 6 16:05:42 GMT 2017
Martin Gräßlin wrote:
> For packagers it should not matter at all. This is the most common
> situation for distribution. And in the release of e.g. Plasma they have to
> handle this for hundreds of updated dependencies.
> It's also not unexpected, because we have a dependency freeze in place
> prior to the release, thus the dependencies are announced way ahead.
> It's only a "problem" for distros if they want to backport to an older
> release as in the case of Fedora. Honestly I consider this unreasonably.
> If you don't have a problem with backporting hundreds of packages I don't
> think that the one additional package is a problem.
The problem is that core packages such as xkbcommon are maintained by
different people than the Qt/KDE stack. It is not always possible for the
KDE maintainers to get such non-KDE dependencies updated in stable releases
(or in the worst case, even in Rawhide).
More information about the kde-core-devel