questions on deps for kmymoney-5.0.9999 [kde overlay]

genterminl

I've been trying to follow recent kmymoney development, but some time in the past few months, the 5.0.9999 ebuild from the kde overlay has started requiring several unstable frameworks:

asturm · Developer Joined: 05 Apr 2007 Posts: 9337

Recently, kde-apps/kcalcore and kde-apps/kcontacts were moved into KDE Frameworks as kde-frameworks/kcalendarcore and kde-frameworks/kcontacts.

All kde overlay ebuilds were already switched over to accept the KDE Frameworks versions only.

genterminl · Posted: Tue Oct 29, 2019 1:32 pm Post subject:

I understand that would account for new frameworks on the list, and while I haven't tested my own compile against those new frameworks (vs as application(s,) my question is why all these frameworks require unstable versions?

Also, the issue of aqbanking and gwenhywfar versions is unrelated to the frameworks question.

asturm · Developer Joined: 05 Apr 2007 Posts: 9337

Frameworks in Tier 2 and 3 always depend on the same version of other Frameworks, this is enshrined in their build system. Same as you wouldn't expect a mix of Qt 5.12.3 and 5.12.5 as well.

Question about live ebuild dependencies is moot, if you do development on kmymoney you are in the best position to just submit a PR to kde overlay. Live ebuilds are fetching moving targets and they don't write themselves - help always welcome! But if you sync again, you'll see there have already been changes.

genterminl · Posted: Tue Oct 29, 2019 4:58 pm Post subject:

Thanks. I just synced yesterday, but haven't actually tried KMM since that. I'll sync again before my next look. I do participate in the kde-devel list, so I suppose I'll have to get myself set up for PR's on the overlay. (I do docs, not actual code development, but I can still help pass on current changes in deps. Hopefully a new sync will answer some of my questions, but I wasn't asking why any ~ framework would only depend on other ~ frameworks, but why KMM 5.0.9999 would depend on unstable frameworks, when (with possible rare exceptions) KMM itself (even git head, especially 5.0 branch) doesn't need them. Also, I don't follow all the logic of the eclasses, so it wasn't even clear to me exactly where the request for the ~ frameworks was coming from. That's just me still trying to understand all the plumbing.

asturm · Developer Joined: 05 Apr 2007 Posts: 9337

genterminl · Posted: Tue Oct 29, 2019 10:44 pm Post subject:

Yes, that makes sense for new frameworks. However, it seems to mean I can't install KMM 5.0.9999 without allowing lots of my other KDE apps and frameworks to also go to unstable. (I have a mostly stable system, with only select unstable packages.) I suppose I might end up doing that, or else just keep compiling myself, sticking with the kde-apps versions of kcalcore and kcontacts until the stable versions of other kde applications have also gotten upgraded to use the frameworks versions.

asturm · Developer Joined: 05 Apr 2007 Posts: 9337

I would recommend doing the following: