On 07/04/11 at 12:55 +0100, David Greaves wrote: > Package: gem2deb > Version: 0.2.1-1 > Severity: important > > > Note this is a personally built gem2deb but that shouldn't be a factor here. > > The yajl-ruby gem has yajl.rb and yajl.so > > I think gem2deb is responsible for putting the extension into a > consistent place; however, since the names are the same I had to patch > my packaging to change the main yajl.rb from: > require 'yajl/yajl' > to > require 'yajl.so' > > see > https://github.com/lbt/yajl-ruby/blob/debian/debian/patches/0001-debian-changes-0.8.1-1.patch > > In gem2deb 0.1 it would install to: > > /usr/lib/ruby/vendor_ruby/1.8/yajl.rb > /usr/lib/ruby/vendor_ruby/1.8/i486-linux/yajl.so > > in 0.2 it installs to: > /usr/lib/ruby/vendor_ruby/yajl.rb > /usr/lib/ruby/vendor_ruby/1.8/i486-linux/yajl.so > > Which wouldn't be a problem ... but that > > $LOAD_PATH is ["/usr/local/lib/site_ruby/1.8", > "/usr/local/lib/site_ruby/1.8/i486-linux", > "/usr/local/lib/site_ruby/1.8/i386-linux", "/usr/local/lib/site_ruby", > "/usr/lib/ruby/vendor_ruby/1.8", "/usr/lib/ruby/vendor_ruby/1.8/i486-linux", > "/usr/lib/ruby/vendor_ruby", "/usr/lib/ruby/1.8", > "/usr/lib/ruby/1.8/i486-linux", "/usr/lib/ruby/1.8/i386-linux", "."] > > Note that > /usr/lib/ruby/vendor_ruby/1.8 > precedes > /usr/lib/ruby/vendor_ruby/1.8/i486-linux > > but > /usr/lib/ruby/1.8 > supercedes it > > The result of which is that the initial 'require yajl' now pulls in > the yajl.so which succeeds but of course many methods are "just > missing". (This was not easy to find...) > > It would be awfully nice if upstream could call the extension > yajl_ext.so but I wonder if it makes more sense to have all extension > PATH_LOAD entries follow all ruby PATH_LOAD entries by default.
I think that the correct fix is to install the extension to /usr/lib/ruby/vendor_ruby/1.8/i486-linux/yagl/yajl.so But I'm not sure what's the good way to do that... Would it make sense to simply move the .so file after the build? - Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
