> On 21 Feb 2020, at 17:29, Thiago Macieira <thiago.macie...@intel.com> wrote: > > On Tuesday, 18 February 2020 15:44:24 PST Thiago Macieira wrote: >> $ grep -r 'public QProcess' >> kcoreaddons/src/lib/io/kprocess.h:class KCOREADDONS_EXPORT KProcess : public >> QProcess >> khtml/src/java/kjavaprocess.h:class KJavaProcess : public QProcess //QObject >> kpty/src/kpty.cpp:class UtemptProcess : public QProcess >> kwin/utils.h:class KWIN_EXPORT Process : public QProcess >> >> The first two do not override setupChildProcess, the latter two do. > > Do note that the current check means we can't tell that KProcess did not > override setupChildProcess. That means any and ALL users of KProcess will > need > to revert to the older, slower, thread-unsafe, non-pidfd implementation. > > So let me ask again: can we deprecate setupChildProcess() in Qt 5.15 and > *remove it* in 6.0?
I’m fine with that, and as communicated by Jani, deprecations can be done even with feature freeze in effect, with approval from module maintainer (up until Beta1; after that only with Lars’ approval). And I do assume you will approve :) Volker _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
