True, but, it depends of the user. If he don't use any gem, it wont
broke. So, we need decide if we'll provide a new package with many new
features, or wait some time (how much?) to provide this package
because some (how much?) users use a specific gem to code/run a Rails
app.
Yes, it's not an easy question, ideally someone enough involved in the
Rails community should say when it is OK (from Rails point of view) to
upgrade Ruby. I'm definitely not that person I'm afraid, I just wanted
to say that upgrading Ruby has its consequences. I myself don't
use/need any other gems than those that Rails require, at least for
now I don't.
We can alway have a ruby package and a ruby18 package at a later date,
much like what will happen when I make python3 to python. Currently, it
seems that nothing in the repos builds against ruby-1.9 so I (or whoever
takes ruby over) can wait for that transition and provide a ruby19 package.
Allan
02-06-2009, 06:46 AM
Ondřej Kučera
Maintainer wanted for ruby
Hi,
We can alway have a ruby package and a ruby18 package at a later date,
much like what will happen when I make python3 to python. Currently, it
seems that nothing in the repos builds against ruby-1.9 so I (or whoever
takes ruby over) can wait for that transition and provide a ruby19 package.
Well maintaining both versions (at least for some time) would be an
ideal solution, only I didn't dare to suggest it because I can imagine
it takes quite some work. :-)
Ondřej
--
Cheers,
Ondřej Kučera
02-06-2009, 10:34 AM
"Kessia 'even' Pinheiro"
Maintainer wanted for ruby
Hi,
Maintain both version only depends of the developer, he'll maintain
both? And it can broke any actual package?
On Fri, Feb 6, 2009 at 4:46 AM, Ondřej Kučera <ondrej.kucera@centrum.cz> wrote:
> Hi,
>
>> We can alway have a ruby package and a ruby18 package at a later date,
>> much like what will happen when I make python3 to python. Currently, it
>> seems that nothing in the repos builds against ruby-1.9 so I (or whoever
>> takes ruby over) can wait for that transition and provide a ruby19 package.
>
> Well maintaining both versions (at least for some time) would be an ideal
> solution, only I didn't dare to suggest it because I can imagine it takes
> quite some work. :-)
>
> Ondřej
>
>
> --
> Cheers,
> Ondřej Kučera
>
--
Kessia Pinheiro
Computer Science Student - Brazil, UFBa
Linux System Administrator
Arch Linux Trusted User
Linux User #389695
http://even.archlinux-br.org
---
X Fórum Internacional Software Livre - fisl10
24 a 27 de junho de 2009
PUCRS - Porto Alegre - Brasil
02-06-2009, 12:11 PM
Johannes Held
Maintainer wanted for ruby
"Kessia 'even' Pinheiro" <kessiapinheiro@gmail.com>:
> And it can broke any actual package?
Updating to 1.9.1 broke vim (beeing compiled with --enable-rubyinterp.
libruby.so can't be located at startup...)
--
Gru, Johannes
Tglich http://blog.hehejo.de und du fhlst dich gut.
Maintainer wanted for ruby
