On Friday, November 15, 2024 9:03:35 AM CET Timo Röhling wrote: > >It seems that `qt6-declarative-dev`'s `Qt6QmlTargets.cmake` has > >a dependency on content of `qt6-declarative-private-dev`, so why > >not express that dependency in the `qt6-declarative-dev` package?
Qt6QmlTargets.cmake creates two targets. One that you are likely to use and one you are very very very unlikely to need. Also using that very unlikely to need target also gives more work for the rest of Debian down the line. > I think this is the best short term solution, as it accurately > reflects the current state of affairs. I understand the Qt/KDE > Maintainers' desire to keep the private API separate (and I agree > with the notion), but the onus is on them to make it work, not on > CMake to retain loopholes. > > Besides, this keeps the issue contained within a single source > package, so it is easy to drop the workaround as soon as the > underlying problem has been solved, without the need to involve the > CMake maintainers and possibly the Release Team in case the fix will > be delayed beyond the toolchain freeze for trixie. I think it is going to affect all of Qt6-packages, not just Qt6Declarative. At least from a quick glance over other of my Qt6*Targets.cmake with private dev things have the same thing. It is just likely that Qt6Declarative is hit first in finding order. /Sune -- I didn’t stop pretending when I became an adult, it’s just that when I was a kid I was pretending that I fit into the rules and structures of this world. And now that I’m an adult, I pretend that those rules and structures exist. - zefrank
