[MacPorts] #62755: digikam: update to 8.4.0

[MacPorts]

#62755: digikam: update to 8.4.0
----------------------+----------------------
  Reporter:  mascguy  |      Owner:  cgilles
      Type:  update   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  digikam  |
----------------------+----------------------

Comment (by RJVB):

 At this point the easiest way to upgrade the port would be to have it pull
 the official .pkg installer and pull the application from there. Looking
 over the build script I think that the net result is going to be the same:
 the installation of a fully independent .app bundle that may or may not be
 movable.

 Replying to [comment:7 barracuda156]:
 > Replying to [comment:3 cgilles]:
 >
 > I have built now 4.14.0, however it crashes on launch (like many KDE4
 apps, though not all of them):
 > {{{
 > QIODevice::setTextModeEnabled: The device is not open
 > digikam(89086) mac_initialize_dbus: warning: unable to initialize D-Bus
 environment!
 > Error: "/var/tmp/kdecache-svacchanda" is owned by uid 501 instead of uid
 0.
 [...]
 > digikam(89086)/kdeui (kdelibs): Session bus not found
 > To circumvent this problem try the following command (with Linux and
 bash)
 > export $(dbus-launch)
 >
 > Program received signal SIGABRT, Aborted.
 > 0x00b32d48 in __kill ()
 > (gdb) bt
 > #0  0x00b32d48 in __kill ()
 > #1  0x00bd680c in abort ()
 > #2  0x0463a934 in qt_message_output ()
 > #3  0x0321b810 in QDebug::~QDebug ()
 > #4  0x03300f48 in KApplicationPrivate::init ()
 > #5  0x03301878 in KApplication::KApplication ()
 > #6  0x004523c8 in main ()
 > }}}

 That's not a crash, that's an abort. Without debug info in kdelibs4 it's
 impossible to tell why but I suspect the `QIODevice` error might be
 related. Or the simple fact that an attempt is made to run a KDE4
 application without having a session DBus daemon running. I never tried to
 do that but there is a reason why `port notes kdelibs4` says

 **Don't forget that dbus needs to be started as the local user (not with
 sudo) before any KDE programs ''will launch''.
 **

 (note the last 2 words!)

-- 
Ticket URL: <https://trac.macports.org/ticket/62755#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS