Hi, On Fri, May 01, 2015 at 11:49:48PM +0530, Pirate Praveen wrote: > Hi,
> There is a problem with rails-assets-jquery-ui.gmespec > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783508 > Can this be handled by gem2deb by converting dynamic listing to static > listing at build time? > Or is this just specific to this package and I should manually set the > file list? The following is based on my current undertanding of rubygems and gem2deb. Feel free to correct me if I missed something. This is handled by gem2deb when building the package: the gemspec is loaded and interpreted, then the result is saved as the file which is installed under /usr/share/rubygems-integration. When building the package, if no metadata.yml file is found but a .gemspec file is found, it is loaded with Gemspec::Specification.load, which would execute the Ruby code defining the files field. In your case, you work with the ruby-jquery-ui-rails, and the gemspec info for this package is produced by the metadata.yml file. But you added a rails-assets-jquery-ui.gemspec manually in debian/ and copied it under /usr/share/rubygems-integration/all/specifications, without adding a version number in the name and without interpreting it. Do you really need to provide a gemspec with a package name that does not correspond to your package? If yes, then you could create a Ruby script which would load the gemspec file in debian/ interpret it and write it into a file that could be installed directly to usr/share/rubygems-integration. I am wondering if the content of the "files" field in the rubygems-integration files is used/useful. If it is not used, then just replace the shell command by an empty string. Cheers, Cédric
signature.asc
Description: Digital signature
