[ruby-core:32412] Re: Can we convert the standard library to gems?

On Wednesday, September 15, 2010, Marcus Rueckert <[e-mail]> wrote:
> On 2010-09-16 03:36:56 +0900, James Cox wrote:
>> =C2=A0I don't believe the issue is as grave as you suggest. there's no
>> reason that stdlib needs to be at the same release version as ruby; it
>> just needs to be clear what the cutoff points are. However, if i am
>> wrong, the fix is simple: specify to each stdlib maintainer that they
>> are not at liberty to update release versions outside of ruby, other
>> than to specify patch level releases until the newer ruby is made.
>
> this is going to work well....
>

I personally would prefer that stdlib were able to manage revisions by
themselves; it'll be much simpler to see what libraries are
languishing and which flourish. Perhaps ruby gems could store a
manifest of known revisions for each release? Eric or others who hack
on gems may be able to better comment.

Still, the idea is that it should be possible to see each stdlib
individually must be what's important:  being able to distinguish
individual packages and make it possible for distributors and
implementors to roll their own rubies with a common core and custom
library.

James

--=20
James Cox,
Consultant, Raconteur, Photographer, Entrepreneur
t: [phone]  e: [e-mail] w: http://imaj.es/
talk: http://twitter.com/imajes photos: http://flickr.com/imajes