thanks so far, to summarize
- put binaries in a separate directory (obviously)
- use --configdir for the corresponding profile => thanks for that hint
- use a different folder to import the pictures from => makes sense to
avoid incompatible xmps
Does the --configdir option also influence the .cache folder? (although
I don't think that matters)
I have to deal now with compiling binaries etc. and find out about --prefix.
Until now I never did something else than install from repo or ppa.
--
regards
Bernhard
https://www.bilddateien.de
William Ferguson schrieb am 11.12.18 um 01:22:
I'm running ubuntu 18.04 and running multiple versions of darktable.
I have 2.4.4 installed from Pascal's PPA. I've also downloaded and
compiled the current git and installed it at /opt/darktable25. Then
I've got the current release candidate installed at /opt/darktable26.
I created a bin directory in my home directory and made one line
scripts to start the git and release candidates with their own config
directories, i.e.:
~/bin/darktable25
/opt/darktable25/bin/darktable --configdir $HOME/.config/darktable25
~/bin/darktable26
/opt/darktable26/bin/darktable --configdir $HOME/.config/darktable26
and a clean version of the release candidate
~/bin/darktable26c
/opt/darktable26/bin/darktable --configdir $HOME/.config/darktable26clean
I keep my 2.4.4 images in ~/Pictures/Darktable, 2.5 in
~/Pictures/Darktable25, release candidate in ~/Pictures/Darktable26
Anders Lund schrieb am 10.12.18 um 22:18:
Do not attempt my suggestion without backing up your data, most importantly
~/.config/darktable
I'd try this:
Install the development version under a different prefix than normal, to avoid
the stable binarys being overwritten.
Run the development version with a different config directory, that is using the
--configdir <user config directory> option.
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
