[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ A ] [ B ] [ C ] [ next ]
Currently, ruby 1.6 is packaged as ruby
, so this does not follow
this ruby policy. So, we'll do as follows.
Initially, we, ruby maintenance team, will intent to package
ruby1.6
. We'll make ruby1.6
from ruby_1.6.8 with
renaming ruby to ruby1.6.
We also make package ruby-defaults
providing ruby
and
libruby
packages. Ruby
package depends on
ruby1.6
and includes /usr/bin/ruby
symlinked to
/usr/bin/ruby1.6
and this ruby policy text. libruby
package depends on libruby1.6
.
Module packages are packaged as libfoo-ruby1.6
for
ruby1.6, and optionally libfoo-ruby
that depends on
libfoo-ruby1.6
.
Note that old version of libfoo-ruby
and renamed
version of libfoo-ruby1.6
provides files with same
pathnames, so that you must add conflicts & replaces against older
versions. That is, don't forget to add to debian/control:
Conflicts: libfoo-ruby (<< renamed-version) Replaces: libfoo-ruby (<< renamed-version)
Version-dependent ruby programs should depends on ruby1.6
and use
#!/usr/bin/ruby1.6 instead of #!/usr/bin/ruby.
Version-independent ruby program that depends on ruby (>= 1.6) but no upper bound limit such as ruby (<< 1.8) or so, make sure it actually works on ruby1.8. If it works on ruby1.8, it should depend on ruby (>= 1.6), ruby (<< 1.9). If it doesn't work on ruby1.8, it is version dependent ruby program, so it must depend on ruby1.6.
After waiting for a week or so(?), we will change default version of ruby from 1.6 to 1.8. Ruby modules and programs should be modified to work with default version of ruby 1.8.
[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ A ] [ B ] [ C ] [ next ]
Debian Ruby Policy
version 0.0.1.4