On Tue, Feb 10, 2015 at 02:53:48PM +0100, Lucas Nussbaum wrote: > 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//' This is now being used by gem2deb 0.12 which I just uploaded to experimental. Feedback is welcome. > My point is that for new gems, dh-make-ruby should maybe default to the > above heuristic. I think there will be a lot of false positives, for example ruby-rspec includes an `rspec` binary, but we still want it as ruby-rspec. Maybe we could just ask interactively, and use the heuristic you propose to obtain a default value for the prompt. -- Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature