---------- Forwarded message ----------
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Mar 30, 2006 11:29 PM
Subject: Re: Unintentional hype of Ruby irb and ri
To: ruby-talk ML <[EMAIL PROTECTED]>


On Fri, 31 Mar 2006 [EMAIL PROTECTED] wrote:

> Perhaps an inflamatory title - but it answers some simple questions.
>
..   The redhat distribution has the
> packages:
> ruby-docs-1.8.1-7.EL4.2
> ruby-tcltk-1.8.1-7.EL4.2
> ruby-1.8.1-7.EL4.2
> ruby-mode-1.8.1-7.EL4.2
> ruby-devel-1.8.1-7.EL4.2
> ruby-libs-1.8.1-7.EL4.2
> irb-1.8.1-7.EL4.2
> So you might get ruby but not irb.
>
> The authors extol the virtues of ri.  I found that ri File  (or ri
> almost anything) gave:
> No ri documentation found in:

>
> In Redhat Enterprise Linux 4, I was able to resolve the irb problem
> simply by installing the irb-1.8.1-7 package.
>
> 

we use rhe on all our machines and i can tell you this:  the rh ruby
rpms are
broken, broken, broken, broken - do not use them and please complain
to redhat
(i have several times).

all the issues you are seeing are resolved by using almost any
installation
method besides rhe rpms.  it even works on fedora.

i manage about 50 machines and we've taken the compile route -
however, since
all the boxes see a common nfs mount we install only once there.

rhe rpms are really really bad in general and should be avoided - for
example
the image magic packages break (silently) loseless compression of
jp2s...  the
perl rpm has a userland kernel panic causing bug, etc, etc.

we use plain vanilla rhe, installing anything 'important' via
compilation and
have 100% success with this approach.  it's also immune to the
auto-upgrade of
enterprise systems breaking 24x7 systems on a late sunday evening.

the reality is that there is exactly one method of installing ruby, or
anything else for that matter, that will work on any platform:

   ./configure --prefix=dst && make && sudo make install

this becomes __really__ important once one starts installing gems that
auto-compile and then upgrade ruby using rpms - only to have all gems
start
giving bus errors...  correct compilation avoids this entirely in
addition to
allowing multiple ruby versions to be installed (which we require).

sad.  but true.

regards.

-a

prasad





-----------------------------------------------
Next Meeting as on our Website: http://ilughyd.org.in
----------------------------------------------- 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ilughyd/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to