[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Dependency of a single binary package

Taking ruby-taglib2 as just an example, it contains binaries for both
Ruby 1.8 and 1.9.1 in a single package.

% apt-file list ruby-taglib2
ruby-taglib2: /usr/lib/ruby/vendor_ruby/1.8/x86_64-linux/taglib2_ext.so
ruby-taglib2: /usr/lib/ruby/vendor_ruby/1.9.1/x86_64-linux/taglib2_ext.so
ruby-taglib2: /usr/lib/ruby/vendor_ruby/taglib.rb
ruby-taglib2: /usr/lib/ruby/vendor_ruby/taglib2.rb

However, it depends on libruby1.8 or libruby1.9.1.
Should it depend on both?

Although I have little idea on very details of Dependency
interpretation, are users installing ruby1.8.7.334 (latest) and
ruby1.9.2.0 (old) allowed to use this library with the old

% apt-cache show ruby-taglib2
Package: ruby-taglib2
Version: 0.1.3-1
Installed-Size: 112
Maintainer: Debian Ruby Extras Maintainers
Architecture: amd64
Replaces: libtagc0-ruby, libtagc0-ruby1.8
Provides: libtagc0-ruby, libtagc0-ruby1.8
Depends: libc6 (>= 2.2.5), libtagc0 (>= 1.5), libruby1.8 (>= | libruby1.9.1 (>=, ruby1.8 | ruby-interpreter


Daigo Moriwaki   <daigo at debian dot org>

Reply to: