[Rubygems-developers] The case of binary gems and Ruby versions.

Jeremy Hinegardner jeremy at hinegardner.org
Thu Apr 16 22:07:56 EDT 2009


On Thu, Apr 16, 2009 at 05:44:30PM -0700, Ryan Davis wrote:
>
> On Apr 16, 2009, at 16:15 , Eric Hodel wrote:
>
>> I see two solutions:
>>
>> Package two separate gems with an indicator in the name for 1.8 vs 1.9
>>
>> Package a gem with both libraries inside, and add something to 
>> require_paths for 1.8 vs 1.9
>
> or:
>
> package the gem normally (but specifying what version of ruby should be 
> mandatory) and when it uploads it goes to a versioned depot. pure ruby gems 
> go up to a shared depot, binaries go to a versioned one. gem fetch can deal 
> with this since it has the spec already. I think this should be 
> transparent... NOT as another gem source.

This was my thought too.  Solve this in the repo.  Instead of having

    gems/
    latest_specs.4.8.gz
    ...

Have

    gems/
    gems/1.8/
    gems/1.9/
    latest_specs.4.8.gz

Or something along those lines.

enjoy,

-jeremy

-- 
========================================================================
 Jeremy Hinegardner                              jeremy at hinegardner.org 



More information about the Rubygems-developers mailing list