* Olly Betts <o...@survex.com> [160324 22:56]: > On Thu, Mar 24, 2016 at 07:52:56PM +0100, Christian Hofstaedtler wrote: > > * Christian Hofstaedtler <z...@debian.org> [160324 19:08]: > > This might not be completely true; but even if the .so doesn't use > > any of libruby's symbols, it's still built against libruby2.2 and > > ends up in the extension directory of libruby2.2. [..]
> > BTW, there's a pkg-config file if you don't want to go via > > RbConfig::CONFIG; if you do, it appears the relevant snippet is: > > print RbConfig::CONFIG['DLDFLAGS'] + ' ' + > > RbConfig::CONFIG['LIBRUBYARG_SHARED'] + ' ' + RbConfig::CONFIG['LIBS'] > > Thanks very much for this additional detail - I had had a brief look and > failed to grasp what was going awry with the automatic dependency. I > think I now actually understand what's going on. Yeah sorry about that, I was also confused what was going on. Still not too sure what the best way to fix this is. In case your package only builds for a single ruby version (I think that's the case), putting this into debian/control is also an option: | RUBY_DEPENDS := -Vruby:Depends="lib$(firstword $(shell dh_ruby --print-supported))" | | override_dh_gencontrol: | dh_gencontrol -- $(RUBY_DEPENDS) (Probably not the most stable thing to do.) > I'll sort out a fix soon, but if this is/becomes the final blocker for > the transition feel free to NMU something appropriate to get us past > that (I think just a binNMU would do the trick as it should get rebuilt > against ruby2.3). There's not really a rush right now from the transition PoV: there's no dependency and there are some other blockers preventing ruby2.2's removal right now. Thank you once again, -- ,''`. Christian Hofstaedtler <z...@debian.org> : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `-
