On Tuesday 01 December 2015 09:53:06 René J.V. Bertin wrote: > > The entry point into kdeinit is "start kwrite please". kdeinit decides > > whether to do that using the kdeinit module (.so) or the executable. > > So what you're saying is that we should be fine (by design) if I remove the > bit where kdeinit checks to see if it should use the kdeinit module? > For now I've only been looking at launch(), observed it can be called with a > shared library and then ensured that that'd work on OS X too. > I suppose what you are implying is that I should look up the caller path to > see where kdeinit verifies if there is a kdeinit module for the tool it has > been requested to start, and disable that part?
Yes - which is exactly what my suggested patch does, AFAICS. -- David Faure, fa...@kde.org, http://www.davidfaure.fr Working on KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
