* Matt Maguire <[email protected]> [01-28-20 09:11]: > So Patrick, I think the issue is that Subhash had all the scripts from the > contrib archive enabled, but some of them are not very robustly coded and > so fail on a Mac (eg. autostyle will look in darktablerc for a path to the > exiftool binary, and if it doesn’t find it, then on Linux systems only it > will use “which” command to try to locate it. In fact, for macOS it should > also use “which” command, it is only Windows where this method should be > skipped). > > As such, I suggested to only add lua scripts that are actively needed, one > by one as needed, and this makes it easier to identify a badly written > script.
I don't believe "all" is a good approach and cannot fathom why it would be pursued. One should *only* activate scripts that provide a wanted/needed function. Then test for compatability and deactivate if not compatible. > Do you know how these scripts are maintained? Can we use the darktable > issue tracker to document issues and propose a PR that corrects such > problems? Or whom should I contact if I have a PR that addresses issues > with the lua scripts? https://github.com/darktable-org/lua-scripts authors are noted in the lua script headers as are some explanations of usage and requirements -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
