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> "