QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Scarlett Moore
Hi everyone, As we progress through the Qt6 transition I have been trying to keep up on our QML dependencies and I keep tripping over circular dependency nightmare. We switched to a mega package format which includes qml modules. So we have big issues when frameworks like kwin depends on plasma-wor

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Nicolas Fella
On 11/8/23 12:22, Scarlett Moore wrote: Hi everyone, As we progress through the Qt6 transition I have been trying to keep up on our QML dependencies and I keep tripping over circular dependency nightmare. We switched to a mega package format which includes qml modules. So we have big issues when

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Sune Vuorela
On 2023-11-08, Nicolas Fella wrote: > Furthermore, kwin is not a framework, it's part of Plasma, and > dependencies between Plasma components are generally fine. That there is > a circular dependency between plasma-workspace and kwin is not good and > should probably be addressed somehow, but the

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread David Redondo
Am Mittwoch, 8. November 2023, 12:22:33 CET schrieb Scarlett Moore: > Hi everyone, > As we progress through the Qt6 transition I have been trying to keep > up on our QML dependencies and I keep tripping over circular > dependency nightmare. We switched to a mega package format which > includes qml

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Scarlett Moore
I apologize for the header. I have been struggling with QML and a bit frustrated from a packager point of view. It very well may be a bug in our build system. I appreciate all the input thus far. Scarlett On Wed, Nov 8, 2023 at 4:48 AM David Redondo wrote: > > Am Mittwoch, 8. November 2023, 12:22

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Kai Uwe Broulik
(forgot to cross-post kde-devel/distributions) Hi, that WorkspaceComponents is used for a ShadowedLabel which is literally one QML file with a Label and a DropShadow. KWin could just not use that (and build its own) and we’d resolve the issue. Cheers Kai Uwe > From what I am seeing this pa

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Sune Vuorela
On 2023-11-08, Kai Uwe Broulik wrote: > Hi, > > that WorkspaceComponents is used for a ShadowedLabel which is literally > one QML file with a Label and a DropShadow. KWin could just not use that > (and build its own) and we’d resolve the issue. It sounds like either moving that component one le

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Heiko Becker
On Wednesday, 8 November 2023 12:48:32 CET, David Redondo wrote: So the situation right now is that plasma-workspace build depends on KWin and KWin has a runtime dependency on plasma-workspace. I think it's not a full cycle since installing plasma-workspace does not need anything from KWin

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Scarlett Moore
While I have everyone's attention. The part that is getting me ( and our linters ) is qml installation paths seem all over the place For example plasma-framework we have org.kde.plasma.plasmoids which I read in the docs is "identified" qml which states it must be installed into the QML import pat

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Nicolas Fella
On 11/8/23 17:11, Scarlett Moore wrote: While I have everyone's attention. The part that is getting me ( and our linters ) is qml installation paths seem all over the place For example plasma-framework we have org.kde.plasma.plasmoids which I read in the docs is "identified" qml which states it

Re: QML: a packagers nightmare. Assistance please.

2023-11-08 Thread Scarlett Moore
On Wed, Nov 8, 2023 at 9:41 AM Nicolas Fella wrote: > > On 11/8/23 17:11, Scarlett Moore wrote: > > While I have everyone's attention. The part that is getting me ( and > > our linters ) is qml installation paths seem all over the place > > For example plasma-framework we have > > > > org.kde.plas