https://bugs.kde.org/show_bug.cgi?id=406722
Michael Pyne <mp...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
CC| |bcooks...@kde.org
Resolution|--- |UPSTREAM
--- Comment #2 from Michael Pyne <mp...@kde.org> ---
Juan, I took a look at sysadmin/repo-metadata and it seems that kuserfeedback
is part of extragear/libs. So from that perspective kdesrc-build is doing the
right thing.
I know there's been a module or two over time that have been developed outside
of kde/frameworks while they were getting into shape for KF5, but I'm not aware
of any that were deliberately left outside of kde/frameworks/* even while they
were meant to be treated as a part of KF5.
Ben might know more, I've CC'ed him. But if KUserFeedback is meant to be part
of KF5 then I would recommend asking its maintainer to work with
kde-frameworks-devel to get the module proposed for and approved for inclusion
into KF5, and from there the sysadmins can update sysadmin/repo-metadata.
If KUserFeedback is required for kdesrc-build in the meantime, then a
module-set config like this would work, and could be made part of the sample
and generated configuration files:
module-set kf5-frameworks
repository kde-projects
use-modules frameworks kuserfeedback
end module-set
However note that kuserfeedback does not presently contain any dependency data
within kde-build-metadata, that's another thing that would need to be fixed to
work well with kdesrc-build and build.kde.org
--
You are receiving this mail because:
You are watching all bug changes.
