On Fri, Apr 27, 2012 at 02:08:34PM +0200, Cédric Boutillier wrote:
> Hi!
Hi,
> In a few weeks from now, Wheezy will be frozen. One of the goals of the
> Ruby Team for Wheezy is to try to push as far as possible the transition
> to a new policy for Ruby library.
>
> You receive this email because you are listed as the maintainer or
> uploader of a Ruby package which has been detected as not using this new
> policy. See the list of maintainers/packages at the end of this email.
Why didn't you file bugs against these packages? Among other things, it would
have helped you track the progress of this transition. Also, why didn't you
contact us a bit earlier, say, months ago, about this transition? I can't find
anything even on debian-devel or d-d-a, did I miss anything?
> Install locations for libraries
> ===============================
>
> Libraries not bundled with the Ruby interpreters should be installed
> somewhere in /usr/lib/ruby/vendor_ruby directory, instead of
> /usr/lib/ruby/1.8 or /usr/lib/ruby/1.9.1. A Pure Ruby library working
> for all Ruby version would go in /usr/lib/ruby/vendor_ruby. Files
> specific to a version of the interpreter should go in
> /usr/lib/ruby/vendor_ruby/$RUBYVER (vendorlibdir). Code compiled
> specifically for the host architecture should go to
> /usr/lib/ruby/vendor_ruby/$RUBYVER/$ARCH (vendorarchdir).
Why did you keep /usr/lib/ruby as installation directory for pure, architecture
independent, Ruby modules, instead of, say, /usr/share/ruby as per FHS (and
Debian Policy 9.1.1)? (see what Perl and Python packages do, for example).
Anyway, I'm working on updating the ecasound (ruby-ecasound) package right now,
so consider it as "pending".
Cheers
P.S. I'm not subscribed to debian-ruby, so please keep me in CC if you have
something to say me.
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
Attachment:
signature.asc
Description: Digital signature