Hi all, There has been a discussion here about where I for example could stuff my CDBS class. With Esteban also working on one, we have talked and decided to merge them and join our efforts. I have also talked with Jeff Bailey (CDBS maintainer) and he's not to happy about joining it (yet) but is interested in a CDBS 2 class. So I thought, why not follow in GNOME's footsteps (gnome-pkg-tools) and create a ruby-pkg-tools package. What should/can it contain? * /usr/share/cdbs/1/class/ruby-setup.mk: the CDBSv1 class to easily handle the install part of a Ruby Package debianization. * /usr/bin/dh_rdoc: script handling HTML & Ri documentation generation, it can determine whether that is already available upstream or generate it itself and install it to the policy-wise right place. * /usr/bin/dh_ruby: script to determine dependencies, ala dh_python/dh_perl. * some stuff for dh-make-ruby, or maybe an extension for dh_make (don't know if this is possible). * some make files usable to define teams in, for example the team preparing libruby-extras. These can be included to create debian/control from debian/control.in. * /usr/share/doc/ruby-pkg-tools/ruby-policy.html: a HTML version of Ruby's policy. What is it for? With the dh_* tools following the Debian policy, we can let the stuff of this package deal with the Debian/Ruby policy (more on that later this week). A Ruby lib package would just have build-depends on ruby-pkg-tools and optionally the binary headers/libs it needs to have for building the extensions and it's done. Easy come, easy go :) I am ready/willing to create this package. OK, this is partly because I need that class, hehe, but also consider this to be the first step for the team. So what do you guys think? Paul -- Student @ Eindhoven | email: paulvt@debian.org University of Technology, The Netherlands | JID: paul@luon.net >>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
Attachment:
signature.asc
Description: Digital signature