[Pkg-ruby-extras-maintainers] r134 - tools/ruby-pkg-tools/trunk
Paul van Tilburg
paulvt at debian.org
Fri Nov 18 18:37:15 UTC 2005
On Fri, Nov 18, 2005 at 03:47:40PM +0000, Esteban Manchado Velázquez wrote:
> On Tue, Nov 15, 2005 at 11:20:06PM +0100, Paul van Tilburg wrote:
> > [...]
> > > > So (2) requires a patch for setup.rb that also should be sent upstream.
> > > > IMO it is right for distclean to call `clean' hooks additional to the
> > > > `distclean' hooks.
> > >
> > > Yes, it seems reasonable. Anyway, can we just call clean and distclean for
> > > now (alway upgrading to a sensible setup.rb version)? Then, when we write the
> > > patch (although there won't be no need, in that case), it should work with
> > > both versions, right?
> > It should, providing the distclean doesn't crash because of the error in
> > the upstream setup.rbs. I'll make some time to patch setup.rb, I already
> > have an improved version lieing around.
> With "both versions" I meant the current "sane" one (I assume it's the
> latest) and the patched one.
> There should be no problems with the latest upstream, right? What I mean
> is that if our problems go away just upgrading the upstream Ruby module to the
> latest upstream setup.rb, and it's _that_ easy, let's just do that. We should
> talk to upstream before doing it, because he could've customized the setup.rb
> script, but...
Well latest upsream has the distclean-crashes-when-data/-is-present problem.
But indeed it's quite easy, doing clean && distclean.
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20051118/e307270a/attachment.pgp
More information about the pkg-ruby-extras-maintainers