Re: RFS: ruby-taglib2 (was ITP)
(ccing debian-ruby@)
On 28/04/11 at 23:46 +0200, Vincent Carmona wrote:
> 2011/4/28 Lucas Nussbaum <lucas@lucas-nussbaum.net>:
> > On 28/04/11 at 20:50 +0200, Vincent Carmona wrote:
> >> Hi.
> >>
> >> I have filled an itp bug [1] for ruby-taglib2.
> >> Can I add this package to the team repo ?
> >
> > Sure
> >
> >> The old ruby-taglib was removed from debian (libtagc0-ruby1.8 package).
> >> I think ruby-taglib2 binary package should Provides/Replaces/Breaks
> >> libtagc0-ruby{,1.8} as
> >> - it does breaks libtagc0-ruby1.8 and users can still have it installed
> >> - ruby-taglib2 provides a compatibility with ruby-taglib if it is
> >> called by "require 'taglib'" and not "require 'taglib2'"
> >> What do you think?
> >
> > Yes, looks good. You can generate the necessary Provides/Replaces/Breaks
> > with gen-ruby-trans-pkgs (in the gem2deb package).
>
> I used unversionned version of replaces/conflits as ruby-taglib2 do
> and will replace/conflit all versions of ruby-taglib.
> I cannot use transitional binary packages as ruby-taglib2 current
> version (0.1.3-1) is below the last ruby-taglib version (1.1-7).
> But ruby-taglib is allready removed from debian stable and I do not
> think a lot of people use it.
> I have checked that installing ruby-taglib2 remove an ruby-taglib
> binary package.
>
> $ aptitude search ruby | grep tag
> p libexif-ruby - EXIF tag parsing Library for ruby (dummy p
> p libexif-ruby1.8 - EXIF tag parsing Library for ruby1.8
> p libexif-ruby1.9.1 - EXIF tag parsing Library for ruby1.9.1
> p libmp3tag-ruby1.8 - Reading and writing ID3V1.1 tags in MP3 fo
> p libmp3tag-ruby1.9.1 - Reading and writing ID3V1.1 tags in MP3 fo
> v libtagc0-ruby -
> v libtagc0-ruby1.8 -
> i ruby-taglib2 - ruby-taglib2 is a Ruby interface to TagLib
>
> >
> > Lucas
> >
>
> I have update the git repo.
> Can my work be chcked and upload ?
lintian says:
E: ruby-taglib2: description-starts-with-package-name
Could you fix that?
Also, due to the way the source is built, I think that a "require
taglib2" will load taglib2.so, but not taglib2.rb. Isn't that a problem?
Usually, gems solve that by renaming the foo.so to foo-ext.so.
- Lucas
Reply to: