Replies: 1 comment 3 replies
-
Hi @ioquatix, I think it's quite common now for python / JS / etc. packages with large native components to include pre-compiled binaries for the top few most common platforms. OpenCV, PIL, Sharp, NetVips etc. all do this. Is this common in the ruby world? Or do people use separate gems (as you've done here)? I'm a bit unsure. I'd be happy to look into automatically downloading a compatible binary somehow, and/or perhaps moving the Off the top of my head, the obvious questions to think about are:
|
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been maintaining the
vips
gem for a while, and having a self-contained gem was quite good. I'm still okay with doing that but it does require an investment of time. The gem is slow to install as it must compile vips every time. To be honest, this is kind of annoying. But it's also annoying when a system update can break the Ruby gems, so there is a bit of a trade off.I'm wondering if we can make this better some how. I'd be happy for example to transfer the vips gem to you and just release the
ruby-vips
gem asvips
.On the other hand, maybe it makes sense for us to have a self-contained release - and we could work on that direction - perhaps bundling compiled files into the gem to avoid the overhead. I'd like to think there is some value in isolated gems which don't break if system dependencies aren't met/change. That being said, this was much worse (dependency/version hell) ~5 years ago when I made that fork. These days it mostly just works on all platforms.
I don't really have a strong opinion about this but I wanted to start a conversation about it to see if there was something worth investing time and energy into.
cc @jcupitt
Beta Was this translation helpful? Give feedback.
All reactions