https://bugs.kde.org/show_bug.cgi?id=430949
--- Comment #8 from Hackintosh HD <hackintos...@posteo.eu> --- (In reply to caulier.gilles from comment #3) > Hi, > > Yes, the new relocatable PKG for MAcOS remove older place to install digiKam > : /opt/digikam. No need to use 800Mb for nothing. > > Now bundle is installed in MacOS full compliant place : /Applications. > It can be also installed in other drive if necessary, if space missing. > > Your problem with mysql/mariadb cli tool settings is not only relevant of > MacOS version. If you uninstall Mysql/Mariadb from a Linux Computer, and you > try to restart digiKam, your dysfunction will appear. > > So the ultimate solution is to always check at startup if Mysql/Mariadb CLI > tool are present on host computer. If not, the database settings page must > be show before to continue. > > Also path to found Mysql/Mariadb under MacOS must be adjusted in source code > to follow new install place. > > Gilles Caulier Thank you, Gilles, for fixing the problem that fast, it's highly appreciated. I'll definitely test the next 7.2.0-rc build from https://files.kde.org/digikam/, once it incorporates your commits and will report back (unfortunately, today's digiKam-7.2.0-rc-20201230T073859-MacOS-x86-64.pkg didn't include your commits yet as it was built a few minutes before them). Not to be misunderstood, I think it's a really good idea to move the binaries formerly installed to /opt/digikam to the inside of digiKam's macOS app bundle and thus achieving compliance with the regular macOS app structure. That may help to avoid the casual users' "Where did that /opt-leftover-folder come from? - Nevermind, let's delete it!"-type of accidents. -- You are receiving this mail because: You are watching all bug changes.
