[DRE-maint] ruby-pkg-tools 0.13: request for review

Paul van Tilburg paulvt at debian.org
Mon Dec 24 09:00:56 UTC 2007


Hello, 
On Mon, Dec 24, 2007 at 09:20:27AM +0100, Lucas Nussbaum wrote:
> On 15/12/07 at 12:44 +0100, Arnaud Cornet wrote:
> > > I just implemented Gunnar's suggestion about using packaged setup.rb to
> > > build Ruby packages that doesn't provide one if the maintainer wants to.
> > 
> > [...]
> 
> I've tried to rebuild all our packages with the new ruby-pkg-tools. [...]
> The problem is probably that the setup.rb shipped in the package is too
> old.
> 
> I think that the easiest way to solve that would be to autodetect if the
> version of setup.rb shipped in the package is supported or not (using
> ruby setup.rb --version) and overwrite it if not supported.
> But that's a lot of black magic. Maybe we should just provide a way to
> override the package's setup.rb with libsetup-ruby's one.
> 
> What do you think?

In essence, if you know that a package uses the setup.rb directory
structure, you can use the packaged version which will always be "the
best one" to use.  Note that since the first install.rb, nothing changed
in the meaning of the directory, only new ones get added.  So, because
you make the choice of using setup.rb at one point when creating
debian/rules, you might as well always use the packaged one IMO.

Regards,
Paul

-- 
PhD Student @ Eindhoven                     | email: paulvt at debian.org
University of Technology, The Netherlands   | JID: paul at luon.net
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181



More information about the Pkg-ruby-extras-maintainers mailing list