On Wed, 18 Nov 2020 at 10:16, Tor Arne Vestbø <[email protected]> wrote: > > > > > On 18 Nov 2020, at 14:01, Lisandro Damián Nicanor Pérez Meyer > > <[email protected]> wrote: > > > > On Wed, 18 Nov 2020 at 09:58, Tor Arne Vestbø <[email protected]> wrote: > > [snip] > >> Let’s clarify this, so we’re talking about the same thing: > >> > >> 1. Application end-users > >> 2. Application developers using Qt > >> 3. Qt developers > > > > Let me expand it: > > > > 1. Application end-users > > 2.1. Application developers using Qt as provided by distro. > > 2.2. Application developers using more than one Qt major/minor version. > > 3. Qt developers. > > > >> #3 develops Qt for use by #2 to produce applications for #1 > >> > >> When you are talking about end users, which one of these do you refer to? > > > > 1 and 2.1. > > The application end user (#1) shouldn’t need access to any of Qt’s binaries > AFAIK. What’s there for us to fix for them?
qdbus can be called by an app ran by an end-user. Yes, it's a backwards-compatible tool so nothing to worry with that specific tool (in fact this thread helped to clear down the tools that need to be backwards compatible). So (#1) is mostly (fully?) cleared, then we still have (#2.1). -- 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
