You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@avro.apache.org by Arto Bendiken <ar...@gmail.com> on 2010/08/16 09:27:46 UTC
Ruby gem packaging & distribution
I'd like to ask if whoever is in charge of the Ruby packaging of Avro
would be so kind as to upload the missing latest releases (1.3.1,
1.3.2, 1.3.3) to RubyGems.org:
http://rubygems.org/gems/avro
At present, anybody installing the Ruby implementation using `gem
install avro` will be obtaining the 1.3.0 release, which has issues
that manually installing the 1.3.3 release fixed for me.
Also, without new releases being pushed to RubyGems.org as a matter of
course, it is not possible for users to effectively add a dependency
on the Avro gem. Suppose I wanted to publish a Ruby library "foobar"
that depended on avro >= 1.3.3; when my users attempted to install my
gem with `gem install foobar`, the installation would fail since the
Avro dependency could not be resolved and obtained, not being
registered with RubyGems.org. This state of affairs is certain to
adversely affect uptake of Avro amongst the Ruby community.
In case nobody is currently in charge of the Ruby packaging, I'd be
happy to contribute where I can.
Best regards,
Arto
--
Arto Bendiken | http://ar.to/
Re: Ruby gem packaging & distribution
Posted by Arto Bendiken <ar...@gmail.com>.
On Wed, Aug 18, 2010 at 10:11 AM, Jeff Hodges <jh...@twitter.com> wrote:
> Pushed out avro 1.3.3. Will be documenting the process tomorrow.
Thanks, Jeff, much appreciated!
--
Arto Bendiken | http://ar.to/
Re: Ruby gem packaging & distribution
Posted by Jeff Hodges <jh...@twitter.com>.
Pushed out avro 1.3.3. Will be documenting the process tomorrow.
On Mon, Aug 16, 2010 at 9:52 AM, Jeff Hodges <jh...@twitter.com> wrote:
> Yeah, lemme get on this today.
>
> On Aug 16, 2010 12:28 AM, "Arto Bendiken" <ar...@gmail.com> wrote:
>> I'd like to ask if whoever is in charge of the Ruby packaging of Avro
>> would be so kind as to upload the missing latest releases (1.3.1,
>> 1.3.2, 1.3.3) to RubyGems.org:
>>
>> http://rubygems.org/gems/avro
>>
>> At present, anybody installing the Ruby implementation using `gem
>> install avro` will be obtaining the 1.3.0 release, which has issues
>> that manually installing the 1.3.3 release fixed for me.
>>
>> Also, without new releases being pushed to RubyGems.org as a matter of
>> course, it is not possible for users to effectively add a dependency
>> on the Avro gem. Suppose I wanted to publish a Ruby library "foobar"
>> that depended on avro >= 1.3.3; when my users attempted to install my
>> gem with `gem install foobar`, the installation would fail since the
>> Avro dependency could not be resolved and obtained, not being
>> registered with RubyGems.org. This state of affairs is certain to
>> adversely affect uptake of Avro amongst the Ruby community.
>>
>> In case nobody is currently in charge of the Ruby packaging, I'd be
>> happy to contribute where I can.
>>
>> Best regards,
>> Arto
>>
>> --
>> Arto Bendiken | http://ar.to/
>
Re: Ruby gem packaging & distribution
Posted by Jeff Hodges <jh...@twitter.com>.
Yeah, lemme get on this today.
On Aug 16, 2010 12:28 AM, "Arto Bendiken" <ar...@gmail.com> wrote:
> I'd like to ask if whoever is in charge of the Ruby packaging of Avro
> would be so kind as to upload the missing latest releases (1.3.1,
> 1.3.2, 1.3.3) to RubyGems.org:
>
> http://rubygems.org/gems/avro
>
> At present, anybody installing the Ruby implementation using `gem
> install avro` will be obtaining the 1.3.0 release, which has issues
> that manually installing the 1.3.3 release fixed for me.
>
> Also, without new releases being pushed to RubyGems.org as a matter of
> course, it is not possible for users to effectively add a dependency
> on the Avro gem. Suppose I wanted to publish a Ruby library "foobar"
> that depended on avro >= 1.3.3; when my users attempted to install my
> gem with `gem install foobar`, the installation would fail since the
> Avro dependency could not be resolved and obtained, not being
> registered with RubyGems.org. This state of affairs is certain to
> adversely affect uptake of Avro amongst the Ruby community.
>
> In case nobody is currently in charge of the Ruby packaging, I'd be
> happy to contribute where I can.
>
> Best regards,
> Arto
>
> --
> Arto Bendiken | http://ar.to/