Summary: | kde-apps/akregator: bundles dev-db/metakit | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Coacher <itumaykin+gentoo> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://cgit.kde.org/akregator.git/tree/plugins/mk4storage/metakit | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Coacher
2016-05-14 10:37:30 UTC
dev-db/metakit has no maintainer atm. I am willing to step up if KDE team is interested in unbundling it from akregator. Upstream repo https://github.com/jcw/metakit/commits/master has no commits since 2015, seems dead to me compared to kdepim.git where at least some maintenance happened this year. I doubt that unbundling makes sense in this case. Should we treeclean it then? Dependency from kde-apps/kdepim-meta should be dropped, is KDE team ok finally with its removal? We have no dependency on dev-db/metakit at all. it has a dependency on kde-apps/akregator, or were you referring to the removal of splitted metakit package and not akregator? This bug as I understand $summary is clearly not about akregator removal, it is an integral part of the KDE PIM suite. I think there is a misunderstanding. kde-apps/akregator works fine, supported upstream and in Gentoo. This bug is NOT about removal of kde-apps/akregator dev-db/metakit upstream and downstream status is unknown to me. This bug is NOT about removal of dev-db/metakit. This bug is ONLY about the fact that akregator bundles metakit. As commented above, unbundling metakit could be counterproductive. @kde, if there's nothing left to do here, please close as you see fit. Yes, I think we have established it does not make sense to unbundle. |