Re: RFS: libezgtk-ruby - Wrapper Interface of GTK+ for Ruby #2
On Sat, 2004-08-07 at 00:35, Ervin Hearn III wrote:
> I would like to make another request for a sponsor of my libezgtk-ruby
> package. I have gotten my gpg key signed by a DD and have been
> maintaining the unrelated PennMUSH package, which is also looking for a
> sponsor, over the last 9 months. So, I'm not entirely new to the
> process, though this is my first Ruby package.
Tha package itself (at least the contents) seems to be well placed.
However, it has lots of glitches.
First of all, lintian and linda both complain with some errors:
W: libezgtk-ruby source: out-of-date-standards-version 3.6.0
Is it compliant to 3.6.0? Are you sure it is not compliant with 3.6.1.1?
W: libezgtk-ruby: extra-license-file
usr/share/doc/libezgtk-ruby/LICENSE.txt
Why add another license file? That must be well specified on
debian/copyright.
E: libezgtk-ruby: copyright-should-refer-to-common-license-file-for-gpl
You should point your license to existing GPL, in case it is GPL.
W: libezgtk-ruby:
copyright-lists-upstream-authors-with-dh_make-boilerplate
You should specify an Author or Author_(s)_, in other case, you have to
remove `(s)'.
E: libezgtk-ruby: bad-version-in-relation depends: libgtk2-ruby (=
{Source-Version})
Are you pretty sure about your dependencies versions?
Depends: ${shlibs:Depends}, libruby (= ${Source-Version}), libgtk2-ruby
(={Source-Version})
And... what about Build-Depends? You will need, at least ruby to run the
extconf.rb. That's way pbuilder dies there.
Build-Depends: debhelper (>= 4.0.0)
Besides, did you code fixshebang? What for? To put examples in place? Is
dh_installexamples not enough? Is postinst script not enough either?
Are you sure README.Debian should be needed? It says nothing to me.
Obviously all that is to make it complaint with Debian Policy.
Now, Ruby policy: You should at least have read the Debian Ruby Policy
made by the guys from pkg-ruby:
http://pkg-ruby.alioth.debian.org/ruby-policy.html/index.html
Just quickly, you should provide a virtual package for your ruby package
to point to the current ruby version (in these cases, 1.8). And create,
if it could be done, packages for 1.6 and so.
It is widely needed help for Ruby packages, I think you are doing an
excellent work, keep on doing it.
Regards,
--
David Moreno Garza <damog@damog.net> | http://www.damog.net/
GPG 356E16CD - 84F0 E180 8AF6 E8D0 842F B520 63F3 08DB 356E 16CD
Reply to: