Hi Tim. On Fri, Jul 25, 2014 at 03:53:33AM +0000, Potter, Tim (Cloud Services) wrote: > Hi everyone. I'm interested in helping out with Ruby packaging for Debian. > In particular I'm keen on a rather ambitious project - to package > elasticsearch and logstash. There's some work in progress already on the > debian-java list for the Java dependencies, and I thought I would also start > looking at the Ruby gems required for logstash plugins. > My initial list of gems required for the logstash plugins is pretty long > about thirty gems. Too boring to list here? > Just to get my feet wet I've had an initial go at ruby-awesome-print using > the instructions on the Teams/Ruby/Packaging wiki page. > http://anonscm.debian.org/cgit/users/tpot-guest/ruby-awesome-print/ > There appears to be some different in the way dh_ruby runs rspec tests vs > the command line so a patch is required: > --- ruby-awesome-print-1.2.0.orig/spec/spec_helper.rb > +++ ruby-awesome-print-1.2.0/spec/spec_helper.rb > @@ -16,7 +16,6 @@ > # > $LOAD_PATH.unshift(File.dirname(__FILE__)) > $LOAD_PATH.unshift(File.join(File.dirname(__FILE__), '..', 'lib')) > +require 'rspec' > require 'awesome_print' > def stub_dotfile! > I'm not sure whether making a patch using dpkg-source --commit is the > correct approach though. Does anyone care to chime in? There are ways to avoid a patch in this case: What I would recommend is to switch from the yaml method to the rake method (it applies for all packages with rspec tests). A simple debian/ruby-tests.rake file would be these three lines: ----8<---- require 'rspec/core/rake_task' RSpec::Core::RakeTask.new(:spec) task :default => :spec ----->8---- The other way would be to add in this debian/ruby-test-files.yaml one line: - rspec/autorun to the yaml list. Cheers, Cédric
Attachment:
signature.asc
Description: Digital signature