Am Sonntag, dem 19.09.2021 um 17:31 +0200 schrieb Cédric Boutillier: > Hi, > > I have been looking at the bugs on ruby-nokogiri before trying to update > it to the new upstream version. > > Using the gem install layout is not enough to have the > ext/nokogiri/nokogiri.h installed. As I understand it, gem_installer.rb > in gem2deb is removing all sources from the ext/ directory. Actually nokogiri just failed when using the gem installation layout and I wasn't able to fully deal with that yet (one has to remove the tarballs from the created gemfile). So I was thinking about just adding the header. But when nokogiri is installed in the vendor-path, which path should we use to put the header file (nokogiri/nogogiri.h) in? RUBYHDRDIR (/usr/include/ruby-<ver>) SITEHDRDIR (/usr/include/ruby-<ver>/site_ruby) VENDORHDRDIR (/usr/include/ruby-<ver>/vendor_ruby) That would fix the issue at hand and give us time to figure out these questions: > So my questions are: > - should we modify gem2deb to allow for installation of headers file? > (at least maybe the ones added to the WHITELIST) > - if so, should we install them, as the gem command does, in the > /usr/lib/ruby/gems/x.y.z/gems/package-a.b.c/ext subdirectory? > OR > - would it make sense for nokogumbo to use instead Built-Using: to use > the nokogiri.h present in the source package? > > what would be the best strategy for this situation? Regards, Daniel -- Regards, Daniel Leidert <dleidert@debian.org> | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert
Attachment:
signature.asc
Description: This is a digitally signed message part