Dear Antonio, On Thu, May 30, 2013 at 07:13:03PM -0300, Antonio Terceiro wrote: > Hello all, > I have just uploaded gem2deb 0.4.0 to unstable. This new release adds > support for multi-binary packages to dh_ruby. I will quote here the > associated documentation in dh_ruby(1). > [...] > I have taken special care to not break compatibility, so this feature > should not bring any noticeable behaviour change for packages that don't > actually use it. That's why I am uploading directly to unstable instead > of uploading it to experimental first. > If you notice any regression, please report a bug. > If you have any quations, just reply. Thanks a lot for working on this. This seems to work very well for packages with .gemspecs in different directories, as explained in the manpage. I have a question about how to use this setting in cases where the different .gemspec files are in the same place (let's say the root directory). I have two examples in mind: ruby-json (which ships also json-pure), and bson/bson-ext/mongo which are developped in the same git repository and would benefit from this functionality, because at the moment, tests for the different libraries are entangled. I've tested with ruby-json. However, indicating two binary packages ruby-json and ruby-json-pure, the two directories debian/ruby-json and ruby-json-pure receive exactly the same files. I cannot manage dispatch the files in different directories, unless I use DH_RUBY_USE_DH_AUTO_INSTALL_DESTDIR=1 and *.install files. However, with this variable set, I have two issues: - extensions are built in debian/ruby-json / debian/ruby-json-pure instead of debian/tmp (this is related to #701716) - I get warning that this variable is deprecated in favor of the new multibinary setting (this should be indicated in dh_ruby's manpage). What would be the strategy for such situations? Thanks! Cédric
Attachment:
signature.asc
Description: Digital signature