2010/9/9 Aaron Patterson <aaron / tenderlovemaking.com>:
> On Thu, Sep 09, 2010 at 12:45:50PM +0900, Yusuke ENDOH wrote:
>> >> =A0cons:
>> >> =A0 1) disadvantage for the core team: developping style will get
>> >> =A0 =A0 =A0complex. =A0The core team must care multiple entities: Rub=
y
>> >> =A0 =A0 =A0package and stdlib gems.
>> >
>> > I don't think this con is true. =A0Development of these gems could sta=
y in
>> > the Ruby svn repository. =A0There is no reason to keep them in separat=
e
>> > repositories. =A0Gem releases could be made from the Ruby source itsel=
f.
>> > Gem releases would only happen with the ruby-core member in charge of
>> > that stdlib gem deems appropriate.
>>
>> I agree. =A0Almost all developers will not be affected by this change,
>> except release managers :-)
>
> How would release managers be affected? =A0If I only use ruby svn for
> managing my "stdlib-gem", ruby svn *always* has the most up-to-date
> version of the code, =A0chkbuild will always run my tests, life would
> continue the same (I think).

We have a solution named "default gems".
rake, rdoc and minigest.
(but I don't know details)

--=20
NARUSE, Yui
naruse / airemix.jp