On 10/02/15 at 11:49 -0200, Antonio Terceiro wrote: > On Mon, Feb 09, 2015 at 08:32:51PM +0100, Lucas Nussbaum wrote: > > On 07/02/15 at 00:33 +0530, Balasankar C wrote: > > > Isn't pry one gem like rails and rake? Don't know if it is relevant. > > > > Couldn't there be a heuristic that goes a bit further? > > > > by default, use ruby-$GEMNAME > > but if there's an executable called $GEMNAME, then use $GEMNAME > > I just uploaded ruby-foreman to NEW, and it contains a foreman > executable. :) > > I went to look inside python-stdeb (the equivalent of dh-make-ruby for > Python), and it uses apt-file to determine package names by looking for > the *.egg-info files for the upstream dependencies. That's definitively > something we want to do. > > This produces a reasonable mapping: > > apt-file search /usr/share/rubygems-integration/ | sed -e 's#/.*/##; s/-[0-9.]\+.gemspec//' Sorry, I wasn't thinking straight. My point is that for new gems, dh-make-ruby should maybe default to the above heuristic. For dependencies, what you suggest seems much more robust, indeed. Lucas
Attachment:
signature.asc
Description: Digital signature