[DRE-maint] ruby-setup-rb.mk, and ftbses

Antonio Terceiro terceiro at softwarelivre.org
Sun Jan 13 00:14:58 UTC 2008


Hi,


Arnaud Cornet escreveu isso aí:
> 
> Le samedi 12 janvier 2008 à 23:51 +0100, Lucas Nussbaum a écrit :
> > On 12/01/08 at 23:40 +0100, Arnaud Cornet wrote:
> > > > This doesn't work. The idea is to always use setup.rb from the package.
> > > > Using upstream's setup.rb will make us use old versions of setup.rb,
> > > > which won't support some of the options we use.
> > > 
> > > That's not what is currently implemented at all then.
> > 
> > Yes, but that's what we kind-of decided after I tested all our packages
> > with the version of ruby-pkg-tools in the repository, I think...
> 
> 
> You and Paul seem to agree on that. I'm worried of bad behaved upstreams
> that hack around setup.rb but hey you have do settle down on something.
> 
> I just commited in the ruby-setup-rb.mk class code  that enforces the
> use of libsetup-ruby's setup.rb.

I think I have a simpler solution. What to you think about just:

--- 1/class/ruby-setup-rb.mk    (revisão 2419)
+++ 1/class/ruby-setup-rb.mk    (cópia de trabalho)
@@ -35,7 +35,7 @@
 include /usr/share/ruby-pkg-tools/1/class/ruby-common.mk
 
 PACKAGED_RUBY_SETUP_CMD = /usr/lib/ruby/1.8/setup.rb
-DEB_RUBY_SETUP_CMD = setup.rb
+DEB_RUBY_SETUP_CMD = debian-setup.rb
 DEB_RUBY_CONFIG_ARGS = --installdirs=std
 DEB_RUBY_CLEAN_TARGET = distclean


This way we don't touch upstream's setup.rb and don't have to check anything
else.

I still need to check if all the packages build with this change. BTW, what is
the most practical way to do that?

-- 
Antonio Terceiro <terceiro at softwarelivre.org>
http://people.softwarelivre.org/~terceiro/
GnuPG ID: 0F9CB28F





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