Looking to re-open the discussion around libraw/rawkit. Distros (currently Fedora, eventually Ubuntu) are packaging the latest libraw 0.19.x.
I see the raphodo release note regarding newer versions of libraw (breaking python rawkit) and have read through the history from 2017 regarding libraw 0.18 and the rawkit incompatibilities at that time.
Unlike 2017, rawkit is now marked unmaintained and there hasn’t been any activity there since (Commits · photoshell/rawkit · GitHub).
Arch is carrying a vendor patch to make libraw 0.19 work (https://git.archlinux.org/svntogit/community.git/tree/trunk/libraw19-support.patch?h=packages/python-rawkit) however Fedora (my preferred distro) is currently broken. I’m looking at a temp workaround in Fedora: either apply the Arch patches locally (since Fedora upstream is unlikely to keep patches like that around) or install libraw 0.18 and use path tricks to get raphodo running for now.
What I’d like to investigate here (or I can move the discussion to launchpad if @damonlynch prefers) is the longer term path forward.
Do we attempt to get photoshell to turn over mantainership?
Should raphodo maintain its own libraw bindings for just the features used?
Is there some better maintained libraw python package that could be used / contributed to instead? I looked through pypi and there are a couple more active (and significantly less mature) projects.
Is there some better path forward that isn’t as obvious (to me) as the above options? Does @damonlynch already have something in the works?
I’m willing to help with some of the coding / distro packaging as time allows. Need a sustainable path forward to begin designing / coding around. Thanks All!