D5775: Don't include the pid in the dbus path when on flatpak

[Aleix Pol Gonzalez]

apol added a comment.


  In https://phabricator.kde.org/D5775#108938, @jgrulich wrote:
  
  > Problem is that the name, even when the pid would be unique, won't be predictable. You still need to change it to something like org.kde.appName.pid so you can use org.kde.appName.* in flatpak manifest. Problem is that you need to allow to own those dbus services and because of that the first instance won't let the other instance to register itself.
  
  
  Right, so the PID is not what we want maybe. I have the impression that the usage of PID here is a bit random though, the important thing is to be able to expose all okular instances to dbus.

REPOSITORY
  R271 KDBusAddons

REVISION DETAIL
  https://phabricator.kde.org/D5775

To: apol, #frameworks, jgrulich
Cc: aacid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20170512/a0494419/attachment.html>