/usr/bin/dh_ruby is in gem2deb 0.6.1.
This file is owned by root:root, with mode 0o755.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 | #!/usr/bin/ruby -w
#
# Copyright © 2011, Lucas Nussbaum <lucas@debian.org>
#
# This program is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <http://www.gnu.org/licenses/>.
require 'gem2deb'
require 'gem2deb/dh_ruby'
require 'gem2deb/setup_rb_installer'
require 'optparse'
include Gem2Deb
engine = Gem2Deb::DhRuby.new
optparse = OptionParser.new do |opts|
opts.on('-h', '--help', 'show help') do
puts opts
exit
end
opts.on('', '--setuprb', 'use setup.rb for installation') do
engine.installer_class = Gem2Deb::SetupRbInstaller
end
opts.on('-v', '--version', 'show dh_ruby version') do
puts "dh_ruby version #{Gem2Deb::VERSION}"
exit
end
opts.on('', '--print-supported', 'prints supported Ruby versions') do
Gem2Deb::SUPPORTED_RUBY_VERSIONS.keys.sort.each do |v|
puts v
end
exit
end
opts.on('', '--clean', 'debhelper clean helper') do
engine.clean
exit(0)
end
opts.on('', '--configure', 'debhelper configure helper') do
engine.configure
exit(0)
end
opts.on('', '--build', 'debhelper build helper') do
engine.build
exit(0)
end
opts.on('', '--test', 'debhelper test helper') do
engine.test
exit(0)
end
opts.on('', '--install', 'debhelper install helper') do
engine.install(ARGV)
exit(0)
end
end
optparse.parse!
puts optparse
exit(1)
__END__
=head1 NAME
dh_ruby - debhelper7 build system for Ruby software
=head1 SYNOPSIS
B<dh_ruby> [I<OPTIONS>]
=head1 DESCRIPTION
B<dh_ruby> is a Debhelper 7 build system for Ruby software. It will
automatically build and install files contained in Ruby packages, trying to
work as close to Rubygems as possible but respecting Debian standards for Ruby
packages.
dh_ruby can automatically run your tests against all supported Ruby versions,
see the "FILES" section below.
See dh_ruby --help for details.
=head1 SOURCE PACKAGE LAYOUT
B<dh_ruby> supports two different source package styles: single-binary source
packages, and multi-binary source packages.
=head2 Single-binary layout
The default layout is the B<single-binary> layout. This is the layout used by
most Ruby packages upstream, i.e. Ruby code in I<lib>/, executable programs in
I<bin>/, etc. Packages imported from Rubygems using B<gem2deb(1)> will have
this layout.
When using this layout, B<dh_ruby> will install files (Ruby code,
executables, gemspecs) to the I<first binary package> listed in
I<debian/control>.
=head2 Multi-binary layout
B<gem2deb> version I<0.4.0> introduced support for the B<multi-binary>
layout. This layout should be used when you have a set of different Ruby
packages maintained upstream in a single VCS, and you decide that you
also want to maintain a single source package in Debian having the
different components as separate binary packages.
In this layout, the source package contains the separate components in
subdirectories where each of them will use the standard Ruby layout
(I<lib>/, I<bin>/, etc).
This layout does not support creating separate binary packages from the same
root directory. For those cases, see the documentation on
I<DH_RUBY_USE_DH_AUTO_INSTALL_DESTDIR> below.
To indicate that you want to use a multi-binary layout, we have to 1)
list your multiple binary packages in I<debian/control> as usual, and
add an extra-field called I<X-DhRuby-Root> to each binary package
stanza, indicating which directory has to be used as the root for that
binary package.
An example:
Source: mymultibinarypackage
[...]
Package: ruby-foo
X-DhRuby-Root: path/to/foo
[...]
Package: ruby-bar
X-DhRuby-Root: path/to/bar
The corresponding source package should be layed out like this:
foo/
foo.gemspec
lib/
foo.rb
bin/foo
bar/
bar.gemspec
lib/
bar.rb
bin/
bar
Important notes about multi-binary packages and the usage of
I<X-DhRuby-Root>:
=over
=item
If your package uses the multi-binary layout, it must include
`I<gem2deb> (>= 0.4.0~)` in I<Build-Depends>.
B<Version 0.4.0 had a bug in the support for native extensions> in
multi-binary packages, so if your package uses the multi-binary feature
and at least one of the sub-components has native extensions, you must
use `I<gem2deb> (>= 0.4.1~)` in I<Build-Depends> instead.
=item
The path indicated in I<X-DhRuby-Root>, as you have probably guessed by
now, must be relative to the root of the source package.
=item
If any binary package declares a I<X-DhRuby-Root> field, all other
binary packages that don't have one will be ignored by B<dh_ruby>.
=back
=head1 OPTIONS
=over
=item B<--clean>, B<--configure>, B<--build>, B<--test>, B<--install>
Commands called by debhelper at various steps of the build process.
=item B<--print-supported>
Prints the supported Ruby versions.
=item B<-h>, B<--help>
Displays B<dh_ruby> usage information.
=item B<-v>, B<--version>
Displays B<dh_ruby> version information.
=item B<--setuprb>
This option indicates that the build should use I<setup.rb> rather
than the usual gem-based build. To take effect, this option must come
first !
=back
=head1 ENVIRONMENT VARIABLES
=over
=item I<DH_RUBY_IGNORE_TESTS>
This is a space-separated list of tests that dh_ruby will ignore during package
build. The available test names are "require-rubygems" plus the names of all
supported Ruby versions. At the time of writing, only "ruby1.9.1" and ruby2.0
are supported.
If set to "all", all tests will be ignored during the package build.
=item I<DH_RUBY_USE_DH_AUTO_INSTALL_DESTDIR>
If this variable is defined (to anything), dh_ruby will respect the directory
informed by dh_auto_install(1), usually I<debian/tmp>. By default, gem2deb will
install files to debian/I<package>, where I<package> is the first binary
package listed in debian/control.
This is useful for multi-binary source packages that don't conform to
the supported layout (i.e. separate subdirectories each with I<lib>/,
I<bin>/ etc). Using this, all files will be installed to I<debian/tmp>, and
you can them distribute them into separate binary packages by using
I<debian/$package.install> files or explicit shell calls in
I<debian/rules>.
Mixing I<DH_RUBY_USE_DH_AUTO_INSTALL_DESTDIR> and multi-binary layout is
not supported.
=item I<DH_RUBY_GEMSPEC>
Determines which file contain the gem specification with package metadata. By
default, dh_ruby will read metadata from a .gemspec file in the root of source
package directory. You can use this variable to override that if you want to
provide custom metadata for the Debian package.
In the case there are more than one .gemspec in the source package root, you
will I<need> to use DH_RUBY_GEMSPEC to instruct dh_ruby about which one to use.
=back
=head1 FILES
=over
=item debian/I<ruby-test-files.yaml>, debian/I<ruby-tests.rake>, debian/I<ruby-tests.rb>
Theses files can be used to explicitly tell dh_ruby how to run the tests in your
package. When running the tests, dh_ruby will automatically set RUBYLIB to
include the appropriate directories where the package files were installed in
your package to make sure the tests use them instead of the files in the source
directory.
B<Your package can only contain at most one of these files.>
debian/I<ruby-test-files.yaml> must contain a YAML document with a list of test
files to be run. If the package metadata contains an explicit list of test
files, gem2deb(1) will automatically generate this file for you. Example from
ruby-mime-types:
---
- test/test_mime_type.rb
- test/test_mime_types.rb
debian/I<ruby-tests.rake> can be used to run the tests with rake(1). If you use
this file, your package must Build-Depend on the I<rake> package. You can use
anything you would use in a regular Rakefile, but you must define a default
task. gem2deb includes utility test task that makes it easier for you by
creating a default task automatically. Example:
require 'gem2deb/rake/testtask'
Gem2Deb::Rake::TestTask.new do |t|
t.test_files = FileList['test/*_test.rb']
end
If debian/I<ruby-tests.rb> exists, it will be run with each supported Ruby
version, and must finish with a exit status of I<0>, otherwise dh_ruby assumes
the tests failed. A simple example:
require 'test/unit'
require 'mypackage' # if 'mypackage.rb' or 'mypackage.so' was not installed properly, this will fail
class MyPackageTest < Test::Unit::TestCase
def test_features
assert_equal 4, MyPackage.sum(2,2)
end
end
=item debian/I<require-rubygems.overrides>
Fine-tune the "require-rubygems" test. If the package has a very good reason to
actually `require "rubygems"`, you can use this file as a whitelist of files
allowed to have `require "rubygems"`.
This file is expected to contain a YAML document with a list of files that must
be ignored when checking for `require "rubygems"` lines. Example:
---
- debian/ruby-foo/usr/lib/ruby/vendor_ruby/foo.rb
- debian/ruby-foo/usr/lib/ruby/vendor_ruby/foo/rubygems.rg
As you can see above, you have to list filenames based on their corresponding
install locations in the package temporary install directory, i.e.
`debian/${pkg}/..`
=back
=head1 SEE ALSO
L<B<gem2deb>>(1)
=head1 COPYRIGHT AND AUTHORS
Copyright (c) 2011, Lucas Nussbaum <lucas@debian.org>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
|