Ruby module packages should be named for the primary module provided. The
naming convention for a module foo is
libfoo-rubyX.Y
for the package
for the Ruby version X.Y.
Package that includes foo modules in
/usr/lib/ruby/X.Y/
must be named as
libfoo-rubyX.Y
.
Since we don't have version independent module path (Module Path, Section 1.6), you must package
ruby modules for each ruby version even if the module is really version
independent. So, your choice is (1) package only for default version of ruby,
or (2) package for each available versions of ruby. XXX: We don't recommend
that libfoo-ruby
contains files for all available
versions of ruby.
The package name libfoo-ruby
should be used for a dummy
package that depends on
libfoo-rubyX.Y
that is packaged
for default version of ruby X.Y. By using such a dummy
package, user can easily follow upgrading.
Packaged modules available for one particular version of Ruby must depend on
the corresponding librubyX.Y
package. Note
that you should use librubyX.Y
, not
rubyX.Y
, because these modules are available
mod_ruby
or eruby
without /usr/bin/ruby
.
Of course, if the package includes ruby scripts using
#!/usr/bin/ruby. it must depend on ruby
. (FIXME:
such scripts should be packaged separately?)
Debian Ruby Policy
version 0.0.1.4