[Pkg-ruby-extras-maintainers] r118 - website/src

Paul van Tilburg paulvt at costa.debian.org
Thu Nov 3 11:00:54 UTC 2005

Author: paulvt
Date: 2005-11-03 11:00:54 +0000 (Thu, 03 Nov 2005)
New Revision: 118

Include 'en' in the filename so webgen knows it's in English.

Copied: website/src/40.rubygems.en.page (from rev 117, website/src/40.rubygems.page)

Deleted: website/src/40.rubygems.page
--- website/src/40.rubygems.page	2005-11-03 07:28:57 UTC (rev 117)
+++ website/src/40.rubygems.page	2005-11-03 11:00:54 UTC (rev 118)
@@ -1,128 +0,0 @@
-title: Position on RubyGems
-inMenu: false
-h1. Common Position on RubyGems
-h2. RubyGems
-"RubyGems":http://docs.rubygems.org/ is a packaging system for Ruby
-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.
-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
-have been raised by other individuals and GNU/Linux distributions) :
-* Rubygems packages are not compatible with the FHS. Rubygems follows the "one
-directory per package and version" rule.
-* It is not possible to do "normal" (FHS-compatible) installations of rubygems,
-and some ruby software developers have started to distribute their software as
-gems only.
-* Rubygems is source-intrusive. The *require* instruction is replaced by a
-*require_gem* instruction to allow for versioned dependencies. Debian and most
-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.
-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.
-# 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.
-# For the moment we will continue to package Ruby applications and libraries as
-Debian packages from (preferably pristine) upstream sources as it always has
-been done (using *setup.rb* or *install.rb* for example). Users could then
-continue to install their apps the way they are used to (using apt-get), since
-most of them do not care about the language their apps are written in or about
-other ways this application/library is made available.
-# For Ruby developers requiring bleeding edge library versions or libraries
-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.
-# No package in Debian shall use the gem command during package installation
-or build.
-# 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
-(re)packaging work a bit. 
-h2. For reference : file system layout of the rmail package
-h3. Content of /usr/lib/ruby/gems added after the execution of **gem install rmail**
-[ ... this directory contains all the rdoc documentation provided by the librmail-ruby-doc on Debian ]
-[ ... this directory contains all rmail's unit tests, which are packaged as examples in librmail-ruby-doc in Debian ]
-h3. Files in the Debian package librmail-ruby1.8

More information about the pkg-ruby-extras-maintainers mailing list