[gentoo-commits] gentoo commit in xml/htdocs/proj/en/prog_lang/ruby: index.xml

[Alex Legler (a3li)]

a3li        10/05/02 08:54:03

  Modified:             index.xml
  Log:
  Add some more information about RUBY_TARGETS and improve package policy

Revision  Changes    Path
1.12                 xml/htdocs/proj/en/prog_lang/ruby/index.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/prog_lang/ruby/index.xml?rev=1.12&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/prog_lang/ruby/index.xml?rev=1.12&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/prog_lang/ruby/index.xml?r1=1.11&r2=1.12

Index: index.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/prog_lang/ruby/index.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- index.xml	2 May 2010 07:33:48 -0000	1.11
+++ index.xml	2 May 2010 08:54:03 -0000	1.12
@@ -3,41 +3,41 @@
 <?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
 <!DOCTYPE project SYSTEM "/dtd/project.dtd"> 
 <project>
-	<name>Ruby</name>
-	<longname>Gentoo Resources for Ruby</longname>
-	<date>20 Mar 2009</date>
-
-	<author title="Original author">
-	    <mail>nichoj</mail>
-	</author>
+    <name>Ruby</name>
+    <longname>Gentoo Ruby Project</longname>
+    <date>02 May 2010</date>
+
+    <author title="Original author">
+        <mail>nichoj</mail>
+    </author>
 
-	<author title="Author">
+    <author title="Author">
         <mail link="graaff@g.o">Hans de Graaff</mail>
-	</author>
+    </author>
 
-        <author title="Author">
+    <author title="Author">
         <mail link="a3li@g.o">Alex Legler</mail>
-        </author>
+    </author>
 
-	<description>This project provides support for the Ruby programming language.</description>
+    <description>This project provides support for the Ruby programming language.</description>
 
-	<longdescription>
-		<p>
-			The Ruby project maintains packages for <uri link="http://www.ruby-lang.org/en/">Ruby
-			</uri> implementations, libraries and development tools.
-		</p>
-		<p>
-			This project also maintains the <uri link="http://rubygems.org/">RubyGems</uri> package,
-			the de facto standard for packaging Ruby projects. Many Ruby packages currently in the
-			Portage tree use this mechanism for installing.
-		</p>
-		<p>
-			Highlighted packages include <uri link="http://rake.rubyforge.org">Rake</uri>,
-			<uri link="http://rubyonrails.org/">Ruby on Rails</uri>,
-			<uri link="http://www.capify.org/">Capistrano</uri>,
-			and <uri link="http://rspec.info/">RSpec</uri>, to name a few.
-		</p>
-	</longdescription>
+    <longdescription>
+        <p>
+            The Ruby project maintains packages for <uri link="http://www.ruby-lang.org/en/">Ruby
+            </uri> implementations, libraries and development tools.
+        </p>
+        <p>
+            This project also maintains the <uri link="http://rubygems.org/">RubyGems</uri> package,
+            the de facto standard for packaging Ruby projects. Many Ruby packages currently in the
+            Portage tree use this mechanism for installing.
+        </p>
+        <p>
+            Highlighted packages include <uri link="http://rake.rubyforge.org">Rake</uri>,
+            <uri link="http://rubyonrails.org/">Ruby on Rails</uri>,
+            <uri link="http://www.capify.org/">Capistrano</uri>,
+            and <uri link="http://rspec.info/">RSpec</uri>, to name a few.
+        </p>
+    </longdescription>
 
     <recruitment>
         <job>
@@ -81,170 +81,193 @@
     <resource link="http://overlays.gentoo.org/proj/ruby/wiki">Ruby overlay and project wiki</resource>
     <resource link="http://gems.stingray.a3li.info/">RubyGem ebuilds needing an update</resource>
 
-	<task id="ruby-1.9" finished="no" lead="a3li">
-		<name>Ruby 1.9</name>
-		<description>Support for all Ruby packages with 1.9</description>
-		<longdescription>
-		  <p>
-  		  Ruby 1.9.1 is going to be the first stable release of Ruby 1.9, to be released in January 2009.
-
-                  Our infrastructure is currently being updated, so we should have ebuilds in the near future.
-          	  </p>
-		  </longdescription>
-		<startdate>12-29-2007</startdate>
-		<milestone finished="yes">
-		  <enddate></enddate>
-		  <description>Package Ruby 1.9</description>
-		</milestone>
-		<milestone finished="no">
-		  <enddate></enddate>
-		  <description>Create new eclasses</description>
-		</milestone>
-                <milestone finished="yes">
-                  <enddate></enddate>
-                  <description>Have a working way to switch default symlinks. Done with eselect-ruby.</description>
-                </milestone>
-                <milestone finished="no">
-                  <enddate></enddate>
-                  <description>Verify USE_RUBY status for all packages in the tree</description>
-                </milestone>
-	</task>
-	
+    <task id="ruby-1.9" finished="no" lead="a3li">
+        <name>Ruby 1.9</name>
+        <description>Support for all Ruby packages with 1.9</description>
+        <longdescription>
+            <p>
+                Ruby 1.9.1 is going to be the first stable release of Ruby 1.9, to be released in January 2009.
+
+                Our infrastructure is currently being updated, so we should have ebuilds in the near future.
+            </p>
+        </longdescription>
+        <startdate>12-29-2007</startdate>
+        <milestone finished="yes">
+            <enddate></enddate>
+            <description>Package Ruby 1.9</description>
+        </milestone>
+        <milestone finished="yes">
+            <enddate></enddate>
+            <description>Create new eclasses</description>
+        </milestone>
+        <milestone finished="yes">
+            <enddate></enddate>
+            <description>Have a working way to switch default symlinks. Done with eselect-ruby.</description>
+        </milestone>
+        <milestone finished="no">
+            <enddate></enddate>
+            <description>Verify USE_RUBY status for all packages in the tree</description>
+        </milestone>
+    </task>
+
     <extrachapter position="devs">
-      <title>Supported Ruby implementations</title>
-      <section>
-        <title>Overview</title>
-        <body>
-          <p>
-          In Gentoo multiple Ruby implementations can co-exist. This
-          is supported through the RUBY_TARGETS mechanism. You can add
-          the RUBY_TARGETS variable to your make.conf file to select
-          which Ruby implementations you want to use on your
-          system. By default only <c>ruby18</c> is selected.
-          </p>
-
-          <pre caption="/etc/make.conf">
-<var>RUBY_TARGETS</var>="ruby18 ruby19"
-          </pre>
-        </body>
-      </section>
-      <section>
-        <title>Ruby 1.8.x (aka MRI): ruby18</title>
-        <body>
-          <p>
-          This version of Ruby is our main implementation. It is
-          available as the 1.8 slot of <c>dev-lang/ruby</c>. It is
-          available in the stable tree, and almost all Ruby packages
-          in the tree are available for this implementation.
-          </p>
-        </body>
-      </section>
-      <section>
-        <title>Ruby 1.9.x: ruby19</title>
-        <body>
-          <p>
-          This version of Ruby is currently still masked pending
-          resolution of some issues. It is available as the 1.9 slot
-          of <c>dev-lang/ruby</c>.
-          <uri link="https://bugs.gentoo.org/show_bug.cgi?id=203706">Bug 203706</uri>
-          tracks the remaining issues.
-          </p>
-          <p>
-            In order to test Ruby 1.9 you will need to unmask the
-            package and also the associated ruby_targets_ruby19 USE
-            flag.
-          </p>
-        </body>
-      </section>
-      <section>
-        <title>JRuby: jruby</title>
-        <body>
-          <p>
-          This version of Ruby is based on the Java Virtual
-          Machine. It is available as <c>dev-java/jruby</c>. It is
-          currently only available in the testing tree.
-          </p>
-        </body>
-      </section>
-      <section>
-        <title>Ruby Enterprise Edition: ree</title>
-        <body>
-          <p>
-            This is an enhanced version of Ruby 1.8, featuring various
-            enhancements, most notably in that it requires less memory
-            to run. It is available as <c>dev-lang/ruby-enterprise</c>.
-          </p>
-        </body>
-      </section>
+        <title>Supported Ruby implementations</title>
+        <section>
+            <title>Overview</title>
+            <body>
+                <p>
+                    In Gentoo multiple Ruby implementations can co-exist. This
+                    is supported through the <c>RUBY_TARGETS</c> mechanism. You can add
+                    the <c>RUBY_TARGETS</c> variable to your <path>/etc/make.conf</path> file to select
+                    which Ruby implementations you want packages to be installed for on your
+                    system. By default only <c>ruby18</c> is selected.
+                </p>
+
+                <pre caption="/etc/make.conf">
+<comment># Installs packages for Ruby 1.8 and 1.9.</comment>
+<var>RUBY_TARGETS</var>=<const>"ruby18 ruby19"</const>
+                </pre>
+                <note>
+                    Some packages do not support all Ruby targets mentioned below.
+                    For example, even if your RUBY_TARGETS setting instructs Portage to install for
+                    both Ruby 1.8 and 1.9, but the package only supports 1.8, the package will only
+                    be installed for Ruby 1.8.
+                    Review the output of <c>emerge -pv &lt;package&gt;</c> to see for which
+                    Ruby versions the package is actually installed.
+                </note>
+            </body>
+        </section>
+        <section>
+            <title>Ruby 1.8.x (aka MRI): ruby18</title>
+            <body>
+                <p>
+                    This version of Ruby is our main implementation. It is
+                    available as the 1.8 slot of <c>dev-lang/ruby</c>. It is
+                    available in the stable tree, and almost all Ruby packages
+                    in the tree are available for this implementation.
+                </p>
+            </body>
+        </section>
+        <section>
+            <title>Ruby 1.9.x (aka MRI/YARV): ruby19</title>
+            <body>
+                <p>
+                    This version of Ruby is currently still masked pending
+                    resolution of some issues. It is available as the 1.9 slot
+                    of <c>dev-lang/ruby</c>.
+                    <uri link="https://bugs.gentoo.org/show_bug.cgi?id=203706">Bug 203706</uri>
+                    tracks the remaining issues.
+                </p>
+                <p>
+                    In order to test Ruby 1.9 you will need to unmask the
+                    package and also the associated <c>ruby_targets_ruby19</c> USE
+                    flag.
+                </p>
+                <impo>
+                    The Gentoo Ruby Team currently does not recommend using Ruby 1.9 for production environments.
+                </impo>
+            </body>
+        </section>
+        <section>
+            <title>JRuby: jruby</title>
+            <body>
+                <p>
+                    This version of Ruby is based on the Java Virtual
+                    Machine. It is available as <c>dev-java/jruby</c>. It is
+                    currently only available in the testing tree.
+                </p>
+            </body>
+        </section>
+        <section>
+            <title>Ruby Enterprise Edition 1.8.x: ree18</title>
+            <body>
+                <p>
+                    This is an enhanced version of Ruby 1.8, featuring various
+                    enhancements, most notably in that it requires less memory
+                    to run. It is available as <c>dev-lang/ruby-enterprise</c>.
+                </p>
+                <p>
+                    In order to test Ruby Enterprise Edition you will need to unmask the
+                    package and also the associated <c>ruby_targets_ree18</c> USE
+                    flag.
+                </p>
+                <p>
+                    For more information, visit <uri link="http://www.rubyenterpriseedition.com/">http://www.rubyenterpriseedition.com/</uri>.
+                </p>
+            </body>
+        </section>
     </extrachapter>
 
     <extrachapter>
-      <title>Policy for adding new Ruby packages</title>
-      <section>
-        <title>Overview</title>
-        <body>
-          <p>
-The ruby herd gets a fair amount of requests to add new packages to
-the dev-ruby category in portage. Unfortunately we often get a bit
-defensive about this and the package requests just hang about. This
-policy tries to outline our thinking on when to add new packages and
-what you can do to enhance the chances of adding a new package.
-          </p>
-        </body>
-      </section>
-      <section>
-        <title>Which packages should go to dev-ruby</title>
-        <body>
-<p>The dev-ruby category should only contain packages that provide
-library code (e.g. dev-ruby/mime-types) and packages that are specific
-to the ruby environment (e.g. dev-ruby/rake).</p>
-
-<p>Specifically, applications written in ruby should *not* go to the
-dev-ruby category by default, and they would not normally be
-maintained by the ruby herd. For example, recently cucumber has been
-added to the dev-util category, even though it is written in ruby and
-started out as a spin of from the more ruby-specific rspec. However,
-it now also has support for Java and it provides an application, so it
-is much better suited for a more targeted category of dev-util.</p>
-
-<p>For libraries and supporting code we tend to add these packages
-only when they are a requirement for an application that gets added to
-Gentoo, or a new requirement of said application.</p>
-
-<p>Other packages only get added when there is sufficient demand. We
-determine this by looking at the number of votes for a package, so
-feel free to open a bug for it and lobby a few folks to add their
-votes.</p>
-        </body>
-      </section>
-      <section>
-        <title>Why not add more packages?</title>
-        <body>
-<p>Having this policy may seem silly. Why not just add new packages as
-people provide ebuilds for them?</p>
-
-<p>In part we are reluctant to add many packages because they should
-really fall under the responsibility of someone else. For example,
-sup, the ruby mail client, fits much better to the net-mail
-herd. After all, not all packages written in C are part of the c
-herd.</p>
-
-<p>In part we are also reluctant because once a package is added it
-will increase our workload towards the future. Version bumps, security
-issues, and QA within Gentoo must be kept up to date. On top of that
-ruby has a bit of a reputation for code that sees a few frantic
-releases and is than for all intents and purposes abandoned. Having
-packages like that in the tree adds disproportionally to our
-maintenance and takes away from providing you with an overall good
-ruby experience on Gentoo.</p>
-        </body>
-      </section>
+        <title>Policy for adding new Ruby packages</title>
+        <section>
+            <title>Overview</title>
+            <body>
+                <p>
+                    The ruby herd gets a fair amount of requests to add new packages to
+                    the dev-ruby category in Portage. Unfortunately we often get a bit
+                    defensive about this and the package requests just hang about. This
+                    policy tries to outline our thinking on when to add new packages and
+                    what you can do to enhance the chances of adding a new package.
+                </p>
+            </body>
+        </section>
+        <section>
+            <title>Which packages should go to dev-ruby?</title>
+            <body>
+                <p>The dev-ruby category should <b>only</b> contain the following packages:</p>
+                
+                <ul>
+                    <li>Library code (e.g. <c>dev-ruby/mime-types</c>)</li>
+                    <li>Packages specific to the Ruby environment  (e.g. <c>dev-ruby/rake</c>)</li>
+                </ul>
+
+                <p>Specifically, <b>applications written in Ruby</b> should <b>not</b> go to the
+                    dev-ruby category by default, and they would not normally be
+                    maintained by the ruby herd. For example, recently cucumber has been
+                    added to the dev-util category, even though it is written in Ruby and
+                    started out as a spin of from the more Ruby-specific rspec. However,
+                    it now also has support for Java and it provides an application, so it
+                    is much better suited for a more targeted category of dev-util.</p>
+
+                <p>For libraries and supporting code we tend to add these packages
+                    only when they are a requirement for an application that gets added to
+                    Gentoo, or a new requirement of said application.</p>
+
+                <p>Other packages only get added when there is sufficient demand. We
+                    determine this by looking at the number of votes for a package, so
+                    feel free to open a bug for it and lobby a few folks to add their
+                    votes.</p>
+            </body>
+        </section>
+        <section>
+            <title>Why not add more packages?</title>
+            <body>
+                <p>Having this policy may seem silly. Why not just add new packages as
+                    people provide ebuilds for them?</p>
+
+                <p>In part we are reluctant to add many packages because they should
+                    really fall under the responsibility of someone else. For example,
+                    sup, the ruby mail client, fits much better to the net-mail
+                    herd. After all, not all packages written in C are part of the
+                    (not even existing) c herd.</p>
+
+                <p>In part we are also reluctant because once a package is added it
+                    will increase our workload towards the future. Version bumps, security
+                    issues, and QA within Gentoo must be kept up to date. On top of that
+                    ruby has a bit of a reputation for code that sees a few frantic
+                    releases and is than for all intents and purposes abandoned. Having
+                    packages like that in the tree adds disproportionally to our
+                    maintenance and takes away from providing you with an overall good
+                    ruby experience on Gentoo.</p>
+            </body>
+        </section>
     </extrachapter>
 
 
-	<dev role="lead">graaff</dev>
-	<dev role="member">robbat2</dev>
-        <dev role="member">a3li</dev>
-        <dev role="member">gengor</dev>
+    <dev role="lead">graaff</dev>
+    <dev role="member">robbat2</dev>
+    <dev role="member">a3li</dev>
+    <dev role="member">gengor</dev>
 
 </project>