On Sun, Sep 19, 2021 at 10:48:47PM +0200, Cédric Boutillier wrote: > Hi Daniel, > > Le Sun, Sep 19, 2021 at 10:13:59PM +0200, Daniel Leidert a écrit : > > Am Sonntag, dem 19.09.2021 um 17:31 +0200 schrieb Cédric Boutillier: > > > 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, I pushed a couple of commits today to fix that: I changed the > 'gemspec' target of debian/rules slightly to call a Ruby script > filtering non-needed dependencies and the ports/* and patches/* parts of > the files metadata. > > Removing the ports/* from the list of files fixed the gem install layout > part. > > Remains the question about where to put the header file (in the gem > install layout context). > > RUBYHDRDIR (/usr/include/ruby-<ver>) > > SITEHDRDIR (/usr/include/ruby-<ver>/site_ruby) > > VENDORHDRDIR (/usr/include/ruby-<ver>/vendor_ruby) > > In the context of an installation under vendor_ruby, I would go for > VENDORHDRDIR, although I would have hoped for a path which does not depend > on the ruby version. nokogiri being a C extension, I think using a ruby version-specific path is the right directory to use. You won't be able to build something against nokogiri and use it with a given Ruby version before nokogiri itself is available for that version.
Attachment:
signature.asc
Description: PGP signature