you should also take care to cleanly separate the darktablerc files at least (possibly run with specific --configdir [.]). otherwise 2.0.x may make the config unusable for the newer version and even lead to crashes.
-jo On Fri, Nov 11, 2016 at 5:10 AM, Karsten Kochan <[email protected]> wrote: > I don't use various installations of darktable but I splitted my database in > configurations for different purposes. I use different folder and create > symlinks via script file instead of starting darktable directly. > > If you manage to have the binaries in different folders you could use the > same approach to keep the configuration and databases apart. > > Best > Karsten > > > Am 2016-11-10 17:05, schrieb Roman Lebedev: >> >> On Thu, Nov 10, 2016 at 7:00 PM, Sascha Oleszczuk <[email protected]> >> wrote: >>> >>> Hi All, >>> >>> is it possible to run darktable 2.2.0 rc0 for testing in parallel to my >>> productive 2.0.7 instance? >> >> Not with the same db and xmp files. >> It is impossible to downgrade, so once you open your 2.0.7 db in 2.2.0rc, >> it will no longer be usable by earlier versions. Same for image edits >> (XMP) >> >>> Thx >>> Sascha >> >> Roman. >> >>> >>> ____________________________________________________________________________ >>> darktable user mailing list to unsubscribe send a mail to >>> [email protected] >> >> >> ____________________________________________________________________________ >> darktable user mailing list >> to unsubscribe send a mail to >> [email protected] > > > ____________________________________________________________________________ > darktable user mailing list > to unsubscribe send a mail to [email protected] > ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
