Cédric Boutillier escreveu isso aí:
> Hi!
>
> I have just joined the team and I am working on my first ruby package: ruby-bluecloth.
> I think the package is (almost?) ready. I have checked that it builds
> fine and works in a clean chroot environment.
>
> I have not enabled the test since they all need ruby-tidy, which is not
> packaged at the moment. The tests contain some "require "rubygems" but I
> believe it is ok. Am I right?
When you are building in a clean chroot environment it is ok because
there will be no gems installed, but you need to take care when building
outside of a chroot to make sure the build did not use libraries
installed by rubygems -- you want to amek sure it works with
Debian-installed Ruby packages only.
> I have a few questions still:
>
> 1/ I produced a simple manpage with pod2man. Is there a better way to
> produce simple manpages? Any tool on which the team agreed on?
IMO pod2man is good enough. That's what we use in gem2deb. Since pod2man
is part of perl and perl already comes in as a build dependency because
of debhelper, there is no extra dependency needed.
> 2/ Most of the tests contain a BEGIN {} block to change the LOAD_PATH
> to include some directory. This causes segfaults when running tests for
> ruby1.8, because the tests load from that directory a binary extension
> built for ruby1.9.1. When the dependencies for running the tests are
> available, should I create patch(es) to comment all these blocks, or is
> there a better/lighter way to do it?
I do not see other way of fixing this without patching the tests.
Ideally it would be nice to talk to upstream to get these patches also
applied by them, but keep in mind that no all Ruby upstreams understand
(or care) about Debian needs.
--
Antonio Terceiro <terceiro@debian.org>
Attachment:
signature.asc
Description: Digital signature