[DRE-commits] r2582 - website/src

[lucas at alioth.debian.org]

Author: lucas
Date: 2008-04-03 08:57:33 +0000 (Thu, 03 Apr 2008)
New Revision: 2582

Modified:
   website/src/40.rubygems.en.page
Log:
minor clarifications on the rubygems web page

Modified: website/src/40.rubygems.en.page
===================================================================
--- website/src/40.rubygems.en.page	2008-04-02 20:44:38 UTC (rev 2581)
+++ website/src/40.rubygems.en.page	2008-04-03 08:57:33 UTC (rev 2582)
@@ -10,9 +10,9 @@
 applications and libraries (similar to CPAN for Perl). It is widely used inside
 the Ruby community (especially inside the "Ruby on
 Rails":http://www.rubyonrails.org/ community), and solves lots of issue
-regarding packaging and distribution of Ruby software.  Rubygems will be
-included in Ruby's standard library in Ruby 1.8.4, and chances are high that it
-will become the de-facto standard for Ruby packaging.
+regarding packaging and distribution of Ruby software on operating systems that don't provide a package manager.  Rubygems will be
+included in Ruby's standard library in Ruby 1.9.1, and chances are high that it
+will become the de-facto standard for packaging and distributing Ruby libraries.
 
 However, the Debian/Ruby Extras team fear that Rubygems will make it much more
 difficult to package and distribute Ruby software in Debian (similar concerns
@@ -28,13 +28,15 @@
 other systems think that dealing with versioned dependencies outside of the
 source is a better idea.
 * There are currently no plans to improve RubyGems to ease the work of Debian
-and RPM packagers.
+and RPM packagers. Some RubyGems developers have also showed hostility
+towards Debian.
 
 h2. Position of the Debian/Ruby Extras Team
 
 # We do not oppose Ruby having a packaging system. However, since Debian has
-its own system already, we prefer to use upstream sources so that we can
-create Debian packages following our current policies.
+its own system already, we feel that it is important that Debian users can
+install all software using the same tools, and that all software installed
+that way follows the same policies.
 # Since we have to follow the FHS, the current RubyGems way of installing the
 gem's contents in one directory is incompatible with our setup (and toolchain)
 and thus cannot be used.
@@ -48,9 +50,12 @@
 that haven't been packaged (yet), a *rubygems* package will be made
 available. This package provides the gem command to be able to install/remove
 gems at the developer's own discretion and risk. The gems will be installed
-using the normal gem installation procedure, in usr/lib/ruby/gems.
+using the normal gem installation procedure, in /usr/lib/ruby/gems.
 # No package in Debian shall use the gem command during package installation
 or build.
+# No package in Debian should require that the user install software as gems.
+This would make it impossible to support (security-wise and quality-wise) such
+software.
 # Other utilities are written to couple the packaging process to the RubyGem
 system, i.e. utilities to help convert a gem to a Debian source package.
 These utilites would not solve any problems, just ease the initial