[ruby-core:37336] I have imported Rake 0.9.2 to trunk

[ruby-core:37336] I have imported Rake 0.9.2 to trunk

[Eric Hodel]

I asked Jim if he would like me to import rake 0.9.2 to trunk, so I have.

Let me know if there are any problems.

PS: I broke `make install` r32217 but fixed it with r32218

[ruby-core:37353] Re: I have imported Rake 0.9.2 to trunk

[Antonio Terceiro]

[-- Attachment #1: Type: text/plain, Size: 453 bytes --]

Hello Eric,

Eric Hodel escreveu isso aí:
> I asked Jim if he would like me to import rake 0.9.2 to trunk, so I have.
> 
> Let me know if there are any problems.
> 
> PS: I broke `make install` r32217 but fixed it with r32218

What are the reasons that led to the inclusion of rake (and e.g.
rubygems) in Ruby's standard library in the first place?

-- 
Antonio Terceiro <terceiro@softwarelivre.org>
http://softwarelivre.org/terceiro



[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[ruby-core:37572] Re: I have imported Rake 0.9.2 to trunk

[Luis Lavena]

On Sat, Jun 25, 2011 at 3:23 PM, Antonio Terceiro
<terceiro@softwarelivre.org> wrote:
> Hello Eric,
>
> Eric Hodel escreveu isso aí:
>> I asked Jim if he would like me to import rake 0.9.2 to trunk, so I have.
>>
>> Let me know if there are any problems.
>>
>> PS: I broke `make install` r32217 but fixed it with r32218
>
> What are the reasons that led to the inclusion of rake (and e.g.
> rubygems) in Ruby's standard library in the first place?
>

Rake has been part of Ruby 1.9.1 and 1.9.2 since their releases. Rake
has become a commonly used tool, like RubyGems.

Ruby also includes JSON as part of it, and RDoc, these tools evolved
form independent ones to be part of Ruby itself with time.

-- 
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éry

[ruby-core:37643] Re: I have imported Rake 0.9.2 to trunk

[Antonio Terceiro]

[-- Attachment #1: Type: text/plain, Size: 2650 bytes --]

Luis Lavena escreveu isso aí:
> On Sat, Jun 25, 2011 at 3:23 PM, Antonio Terceiro
> <terceiro@softwarelivre.org> wrote:
> > Hello Eric,
> >
> > Eric Hodel escreveu isso aí:
> >> I asked Jim if he would like me to import rake 0.9.2 to trunk, so I have..
> >>
> >> Let me know if there are any problems.
> >>
> >> PS: I broke `make install` r32217 but fixed it with r32218
> >
> > What are the reasons that led to the inclusion of rake (and e.g.
> > rubygems) in Ruby's standard library in the first place?
> >
> 
> Rake has been part of Ruby 1.9.1 and 1.9.2 since their releases. Rake
> has become a commonly used tool, like RubyGems.
> 
> Ruby also includes JSON as part of it, and RDoc, these tools evolved
> form independent ones to be part of Ruby itself with time.

I already knew that those things are widely used and that they got
included in Ruby 1.9 ... ;-)

What happens in practice, though, is that people will always install the
latest Rubygems and the latest Rake from within Rubygems, regardless of
the versions included in Ruby 1.9.x

Why I asked this:

I am part of the Debian Ruby packaging team, and we started to discuss
how to deal with the following issue: We have Rubygems and Rake packages
for Ruby 1.8, but not for Ruby 1.9 because they are already included.
What happens then is that users of Ruby 1.8 end up having newer versions
of both Rubygems and Rake, and Ruby 1.9 users end up with whatever
version was included with Ruby, which are often outdated with regard to
the current versions of the standalone packages.

If we decide to make the Debian packages for Rubygems, Rake etc
available for both Ruby 1.8 and Ruby 1.9, we will be in practive
overriding the versions bundled with Ruby. I have the feeling that doing
this reproduces what non-Debian users already do: they install these
packages regardless of the fact they are already bundled with Ruby,
either manually or because some others packages depend explicitly on
them (e.g.  several gems depend on rake, and that will cause Rubygems to
install a standalone rake package).

It has been suggested that Ruby 1.9 could have way of disabling the
bundled packages on ./configure so that they don't get installed on
`make install`, and we could then make the Debian packages explicitly
depend on Rubygems/Rake/etc so that users always get the newest version
of them together with Ruby 1.9.

We don't want to have a Debian-specific patch for that, so we wanted the
opinion of Ruby core. What do people think about that?

-- 
Antonio Terceiro <terceiro@softwarelivre.org>
http://softwarelivre.org/terceiro



[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]