We talked it over with the ruby sig and decided that rails 3.x was probably best for EPEL6. However, since then, I have run into several packages, including ones I use everyday that require rails 2.3.x or it's dependencies. I am proposing to put in rails 2.3.x and then have a rails3 package set when rails 3 is packaged in Fedora and ready to go. Currently, it looks like that might hit for F15, but then will probably take some additional work to get it ready for EPEL.
On a side note, rubygems.org now has as many package as CPAN does for perl. We could really use a lot more ruby packagers.
Also, if you are packaging something for Fedora and don't wish to maintain in EPEL, please email me. I will likely take the EPEL branches.
stahnma
On 25/12/10 17:12, Michael Stahnke wrote:
On a side note, rubygems.org now has as many package as CPAN does for perl. We could really use a lot more ruby packagers.
Wow, mxmas to us all !
Can we have some figures? I thought we were really far awayf from CPAN...
Guillermo
2010/12/26 Guillermo Gómez guillermo.gomez@gmail.com:
On 25/12/10 17:12, Michael Stahnke wrote:
On a side note, rubygems.org now has as many package as CPAN does for perl. We could really use a lot more ruby packagers.
Wow, mxmas to us all !
Can we have some figures? I thought we were really far awayf from CPAN...
Hello:
Michael Stahnke wrote, at 12/26/2010 06:42 AM +9:00:
Also, if you are packaging something for Fedora and don't wish to maintain in EPEL, please email me. I will likely take the EPEL branches.
stahnma
For packages I maintain on Fedora, if you want to own the packages on EPEL, please feel free to do so.
Especially, currently I receive broken deps report about rubygem-activeldap on EPEL6 everyday. To resolve this at least rubygem-locale, rubygem-gettext, rubygem-gettext_activerecord must be imported also into EPEL6. I appreciate it if someone would maintain these on EPEL6.
Regards, Mamoru
On 12/25/2010 04:42 PM, Michael Stahnke wrote:
We talked it over with the ruby sig and decided that rails 3.x was probably best for EPEL6. However, since then, I have run into several packages, including ones I use everyday that require rails 2.3.x or it's dependencies. I am proposing to put in rails 2.3.x and then have a rails3 package set when rails 3 is packaged in Fedora and ready to go. Currently, it looks like that might hit for F15, but then will probably take some additional work to get it ready for EPEL.
The only issue with this is that now for every package that differs depending on the rails version it depends on, we will need two packages in EPEL. This is potentially alot of duplicate packages. Would simply updating those said packages and rails itself to rails 3.0.x work? Is there a deadline for EPEL packages that we need to contend with?
-Mo
ruby-sig@lists.fedoraproject.org
-
"Guillermo Gómez S." -
Mamoru Tasaka -
Michael Stahnke -
Mo Morsi