Ruby

Differences between revisions 1 and 39 (spanning 38 versions)
Revision 1 as of 2005-10-05 09:01:21
Size: 157
Editor: i577B132A
Comment:
Revision 39 as of 2008-08-06 17:00:36
Size: 2133
Editor: localhost
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page describes the efforts of the MOTU Ruby team. ## page was renamed from MOTURuby
MOTURuby is the MOTU team which takes care of the Ruby-related packages.
Line 3: Line 4:
Ubuntu's Ruby Wickedness it brought to you by:
 * ZygmuntKrynicki
 * TrentLLoyd
 * {{{lucas}}}
See our [[https://launchpad.net/people/moturuby|Launchpad team page]] to see the members and other info.

= Use cases =

Lucas wants to use software written in Ruby on his Ubuntu Breezy system. Too bad. Ruby has several important bugs on Breezy, because nobody cared about Ruby packages during the Breezy release process. For example :
{{{
require 'time'
t = Time::parse('2005-08-30T22:50:00-05:00').to_s
=> "Thu Sep 01 05:50:00 CEST 2005"}}}
(As you might know, there are 31 days in august, and this bug has been fixed in Debian for a long time)

So, one month after the Breezy release, Lucas has to start using Dapper packages to see some bugs fixed.

'''We don't want this to happen with Dapper !'''

= Which packages qualify ? =
All packages which depend on ruby, or more exactly libruby1.8, libruby1.6 and libruby1.9. One can easily use [[MultiDistroTools]] to get a list.

See the [[http://tiber.tauware.de/~lucas/versions/ruby-packages.html|Current status of those packages in Ubuntu Dapper]].

= Important packages =

We should focus on important packages and their required libraries. Popularity contest could help here.
Results from the top of my head, feel free to add/modify
 * RubyOnRails
 * Alexandria
 * Of course, the ruby interpreter and all tools needed to develop in Ruby (ruby, irb, rdoc, ri, rake, libraries ...)

= TODO List =
 * FTBFS packages :
  * fix FTBFS as of 2006-01-21 :
   * quantlib-swig (DEPWAIT on libquantlib0-dev)
   * libapache2-mod-xmlrpc2 (FAILED)
   * libintl-gettext-ruby (FAILED) (was 0.11-5. fixed in 0.11-5.1 ?)
  * Re-run builds of everything later.
 * Run piuparts tests on all packages
 * Start working on AutomatedTesting for at least some ruby packages.

= Related team/work =
 * [[http://pkg-ruby.alioth.debian.org/|Debian's pkg-ruby team]] (interpreter, libruby, etc)
 * [[http://pkg-ruby-extras.alioth.debian.org/|Debian's pkg-ruby-extra team]] (some team-maintained ruby packages)

----
CategoryUbuntuTeams [[CategoryMOTU]]

MOTURuby is the MOTU team which takes care of the Ruby-related packages.

See our Launchpad team page to see the members and other info.

Use cases

Lucas wants to use software written in Ruby on his Ubuntu Breezy system. Too bad. Ruby has several important bugs on Breezy, because nobody cared about Ruby packages during the Breezy release process. For example :

require 'time'
t = Time::parse('2005-08-30T22:50:00-05:00').to_s
=> "Thu Sep 01 05:50:00 CEST 2005"

(As you might know, there are 31 days in august, and this bug has been fixed in Debian for a long time)

So, one month after the Breezy release, Lucas has to start using Dapper packages to see some bugs fixed.

We don't want this to happen with Dapper !

Which packages qualify ?

All packages which depend on ruby, or more exactly libruby1.8, libruby1.6 and libruby1.9. One can easily use MultiDistroTools to get a list.

See the Current status of those packages in Ubuntu Dapper.

Important packages

We should focus on important packages and their required libraries. Popularity contest could help here. Results from the top of my head, feel free to add/modify

  • RubyOnRails

  • Alexandria
  • Of course, the ruby interpreter and all tools needed to develop in Ruby (ruby, irb, rdoc, ri, rake, libraries ...)

TODO List

  • FTBFS packages :
    • fix FTBFS as of 2006-01-21 :
      • quantlib-swig (DEPWAIT on libquantlib0-dev)
      • libapache2-mod-xmlrpc2 (FAILED)
      • libintl-gettext-ruby (FAILED) (was 0.11-5. fixed in 0.11-5.1 ?)
    • Re-run builds of everything later.
  • Run piuparts tests on all packages
  • Start working on AutomatedTesting for at least some ruby packages.

Related team/work


CategoryUbuntuTeams CategoryMOTU

MOTU/Teams/Ruby (last edited 2008-08-06 17:00:36 by localhost)