since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Now in feature freeze for upcoming 5.2 release. So please test and report issues …
since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Now in feature freeze for upcoming 5.2 release. So please test and report issues …
since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Now in feature freeze for upcoming 5.2 release. So please test and report issues …
since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
… not much time left for testing upcoming 5.2 release …
since there are already database updates running don’t forget to backup your darktable databases to be able to step back to the latest released version.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
since it’s a bugfix release, don’t expect fancy new features …
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Hi … thanks for all your effort !!!
I am not that good when it comes to the technical side of installation, unless it is straightforward thing with a usual installer !
So I do have a “ maybe “ stupid question of the installation process ?!
Do I need to run the terminal command , before or after the installation of your build ?
This, and the official release, build shows up on my Mac as an IOS application. In the past, official darktable builds were signed and didn’t need a quarantine exception to run. Why?
no idea why it shows up as an iOS app - it’s definitely no correct information.
The packages aren’t notarized because I don’t have a paid apple developer account and the GitHub runner used to build the official packages also doesn’t have it. In former time there was a maintainer with that account
I just share my development builds, take it or leave it, it’s up to you …
Installation is same as for the official packages.just open the package and drag the app file to Application (then it overwrites the official one) or somewhere else.
Next builds here will include agx - so if you don’t want to be a guinea pig for testing that module upcoming in future, then better use the build in darktable 5.2.0 for older macOS versions (10.14 & 11.3 and later)
If you run the “xattr -c” command on the *.dmg file it should open without complaining. Then drag the application to your Applications folder and it should run just fine.
you might run it with an in-memory library via terminal: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory: /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "