On Wed, 18 Nov 2020 at 11:04, Tor Arne Vestbø <[email protected]> wrote: [snip] >> qdbus can be called by an app ran by an end-user. > That sounds like a deployment issue. If the app needs qdbus, it needs to > bundle it, or make sure it knows the full path to it (but that sounds like a > fragile thing to rely on).
Embedding is something that distributions avoid. Getting the full path is possible if exposed somehow (like a CMake variable that holds the path), but it also means the developer must do "the right thing". > Besides, shouldn’t an app using dbus use > https://doc.qt.io/qt-5/qtdbus-index.html and not an external binary? Maybe, but there seems to be use cases: https://sources.debian.org/src/plasma-workspace/4:5.19.5-5/wallpapers/image/wallpaper.knsrc.cmake/?hl=49#L49 just to name one. > So (#1) is mostly (fully?) cleared, then we still have (#2.1). > > > Okey, good to get #1 out of the way first. Thanks! Thanks to you! This really helps everyone discuss the issue! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
