Re: Dealing with upstream only releasing gems

2010-04-09 Thread Roberto C . Sánchez
On Fri, Apr 09, 2010 at 07:06:22PM -0500, Gunnar Wolf wrote: > Paul van Tilburg dijo [Tue, Mar 30, 2010 at 09:11:23AM +0200]: > > > You can easier use githubredir.debian.net to use the github repository > > > as the source, or simply repackage the gem as a tgz. It would be a good > > > thing to hav

Re: Dealing with upstream only releasing gems

2010-04-09 Thread Gunnar Wolf
Paul van Tilburg dijo [Tue, Mar 30, 2010 at 09:11:23AM +0200]: > > You can easier use githubredir.debian.net to use the github repository > > as the source, or simply repackage the gem as a tgz. It would be a good > > thing to have a gem2tgz script that does that automatically, btw. > > AFAIK in t

Re: Dealing with upstream only releasing gems

2010-03-30 Thread Paul van Tilburg
On Tue, Mar 30, 2010 at 07:51:14AM +0200, Lucas Nussbaum wrote: > On 29/03/10 at 19:59 -0400, Roberto C. Sánchez wrote: > > I am working on updates to libmemcache-client-ruby and libi18n-ruby > > (which I did not previously notice were available, on account of both > > upstreams switching to releas

Re: Dealing with upstream only releasing gems

2010-03-29 Thread Lucas Nussbaum
On 29/03/10 at 19:59 -0400, Roberto C. Sánchez wrote: > I am working on updates to libmemcache-client-ruby and libi18n-ruby > (which I did not previously notice were available, on account of both > upstreams switching to releasing only gems a while back). How are > maintainers of Ruby modules in D