Many of us love open-source community projects. If they can’t find somebody able and willing, though, it looks like Darktable for the Mac may be resigned to the history books – at least until and unless somebody pops up in the future to revive it. So, the team is reaching out to find a replacement from within the community that can take on the responsibility. In summary, unless someone steps forwards and commits to the role of OSX maintainer, we will be forced to fully and completely stop supporting OS X, after the next minor release (4.2.1).Īs well as needing a replacement person to deal with the Mac side of things, the reality of compiling for Mac to retain compatibility is becoming more complex and requiring work that nobody else on the team is currently capable of doing. We would like to thank him for all of his efforts!Įverything has it’s limit, and presently, it has been indicated that wants to end that tenure, and pass on the mantle.Īt the same time, there is a big roadblock on the OS X side: currently, as requested by the minimal required XCode version is XCode 12.4 (LLVM10-based), and with LLVM16 about to be released in ~April, that puts us to 7 (sic) LLVM versions to support, in addition to currently supporting three GCC releases. Not only is this support matrix unsustainable, not having a path forward makes it impossible to someday make use of the compiler (and library) features introduced in later compiler versions. Especially, maintenance of the darktable as a whole, on a particular platform.Īs it happens, has been a person solely responsible for maintaining, and packaging, darktable on OS X for the last 10 years. One particular area that is always everyone’s not-first choice is maintenance. A post by Darktable developer Pascal Obry on the Darktable forums on explains the situation.Īs everybody knows, darktable is a community-driven project.
0 Comments
Leave a Reply. |