On Sun, 26 Jan 2020 at 23:26, Subhash Fotografie <fotogra...@subhash.at> wrote:
> [Matt Maguire <matthew.magu...@gmail.com> schrieb am 25.1.2020 um 9:17 > Uhr:] > > >And how exactly are you > >"opening an image" when you see the error message? > > Clicking on "Import image" choosing the image and import it. > > Maybe it has to do with "enable control_exiftool_export" in > "Preferences/LUA options". > I see, you are using LUA scripts, things become clearer :-) The reason I couldn't find references to the exiftool in the code of the buiild I gave you was that the lua scripts you are using are probably stored in your ~/.config/darktable directory. If you have a look at the file ~/.config/darktable/luarc you'll see what scripts are enabled and as Parafin suggested, you can either modify/disable them or see where they are looking for exiftool. > >https://brew.sh/ > > I don't feel comfortable using this. I have a working system here and fear > to mess it up this way. > I'm not a big fan of homebrew either -- I prefer MacPorts, because it doesn't pollute your system directories, and and can delete it simply by removing the whole /opt/local tree. > Why would I need this? Why not just putting exiv2 to this directory? > I don't think you need it -- I was initially thinking before that if you didn't have exiv2 installed, then when darktable doesn't find it maybe it tries to fallback to exiftool. But actually when I searched the code I couldn't find any evidence of this, and it was all very puzzling. The lua script explanation now makes sense :-) ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
