DK on MacOS: Homebrew vs. .pkg installer

[Thomas]

Hi Gilles,

I understand that the PKG is not build with homebrew.

My question is about whether there would be any disadvantages of using 
the homebrew package rather than the PKG?

As mentioned, I see two advantages of using the homebrew package - 
assuming that the user is already using homebrew.

But I fear that there might be some disadvantages.

You mention that the PKG has all features enabled, including 
MySQL/MariaDB, Qt6, Apple Silicon, Latest KDE, ffmpeg, opencv, and HEIF, 
etc. Does this mean that the Homebrew version does not include these? Or 
that it is limited in other ways?


BR

Thomas


On 2025-08-19 14.23, Gilles Caulier wrote:
> Hi,
>
> The PKG is build with Macports not Homebrew. The PKG has all features
> enabled, especially the Mysql/Mariadb support. It's compiled with Qt6,
> support Silicon and always uses last version of Qt and KDE, ffmpeg,
> Opencv, HEIF frameworks.
>
> Best regards.
>
> Gilles Caulier
>
> Le mar. 19 août 2025 à 14:18, Thomas <sdktda at gmail.com> a écrit :
>> Hello,
>>
>>
>> Having used Digikam on Mac via the official .pkg installer from
>> digikam.org for several years, I recently noticed that digikam seems to
>> be available through homebrew as well.
>>
>> Do we have an official recommendation/opinion on when to use the .pkg
>> installer vs. homebrew?
>>
>> Using "brew install digikam" seems to me really nice as it will 1)
>> ensure frequent updates through brew update/brew upgrade, and 2)
>> (hopefully) ensure a much easier installation process in that the user
>> does not have to jump through hoops with MacOS security safeguards
>> against running unsigned applications downloaded from the internet.
>>
>>
>> Are there any drawbacks to using the homebrew package?
>>
>> Of course, the .pkg must still be available for users who for whatever
>> reason do not have homebrew.
>>
>>
>> BR
>>
>> Thomas
>>