Changes between Version 7 and Version 8 of RubySection

Timestamp:

Apr 10, 2009, 6:33:03 PM (15 years ago)

Author:

febeling@…

Comment:

--

RubySection

@@ -1 @@
-''This is an early stage version of a page we could introduce for every major group of ports which should follow certain common principles, and where the involved maintainers can collect the results of their dicussions. I suggest introducing a similar page for Python, Perl, Erlang, and similar cases as well, if it turns out to be useful.''
+''This is an early stage version of a page we could introduce for every major group of ports which should follow certain common principles, and where the involved maintainers can collect the results of their discussions. I suggest introducing a similar page for Python, Perl, Erlang, and similar cases as well, if it turns out to be useful. Feel free to edit as you see fit. --[wiki:febeling]''
 
 == Ruby Section ==
@@ -20 +20 @@
  * There are a number of ruby implementations available, but currently only Matz' Ruby 1.8.7 is invokable just as {{{ruby}}}, or Matz' Ruby 1.9.1 is installed with variant {{{+nosuffix}}}. The variant causes ruby 1.9 to install withuout the suffix, but that makes it conflict with port {{{ruby}}}, i.e. 1.8.7. On the list Brett Eisenberg has suggested fixing that using the same approach as python_select and gcc_select, i.e. by writing configuration symlinks in a PATH location. 
  * To be discussed: should be library ports for ruby generally be avoided in favor of the now ubiquitous gem (part of the 1.9 release)? As said, gems easily break the repositories consistency if packages are not managed exclusively over {{{port}}} or {{{gem}}}.
+
+== Section Maintainers ==
+
+[wiki:febeling] ''add yourself here''