sage
sage
Thanks - I'll make an issue to fix this up and hide these methods
I've released the hiding of these methods in 1.7.0, so closing this issue: https://github.com/lopcode/vips-ffm/releases/tag/v1.7.0
Had a look at how other bindings do this - they seem to just expose the underlying `blob` for access, with a warning about only using it with memory-backed targets,...
Yep sounds good to me 👍
Checking in to see if I can close this issue now, @JohannesBeranek?
I've been thinking about this - there's the version of the bindings, **and** the version of libvips to consider. I wonder if a combined version might make sense, like `0.5.1-vips-8.15.3`?...
I added some description to the README but a specific difference with vips-ffm is it uses the bindings/operations API from libvips - I'm expecting that any VImage (or V(Prefix)) operation...
Did a little more investigation in to a module that would include native libraries, built with GitHub Actions, and it still seems pretty fragile to me - JVips for example...
Just in case this helps anyone else debugging Datadog's Docker support - I bumped in to this limitation setting up Datadog in Nomad, exposing it to other services using Consul...
Had a look, and struggling to figure out the root cause. I added an "Ubuntu 24.04" test to the Docker suite, and that's working OK. Whilst investigating I realised the...