[ruby-core:39482] Re: Modifications to libraries like Rake should be done upstream first

On Mon, Sep 12, 2011 at 12:45 PM, U.Nakamura <[e-mail]> wrote:
> Hello,
>
> r33254 is only workaround for MRI.
> I squeezed this out for MRI, because I'm one of the charges
> who look after MRI.
>

Problem is that issue exist in standalone rake, so newer release that
can be installed on top of MRI can present the issue or the misleading
failure.

> Rake team will make another solution for rake.
> It's rake team's task, but not mine because I'm not a member
> of rake team.
>
>
> I reported this problem to rake team first (I hope the github
> issue page is the right place) , and waited some days.
> I got no response, so I did my work.
>

Hmn, sorry to hear that, actually I sent a pull request a few weeks ago:

https://github.com/jimweirich/rake/pull/72

Also with no response, as you.

> By the way, if there are any problems in the above process, somebody
> who are troubled by the problems will take a certain action, I expected.

Understood.

Thank you for your explanation, will followup with library maintainers.
--=20
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exup=E9ry