In what way does rails depend on readline? It seems a real crutch to
not be able to use the builtin ruby interpreter on os x for rails
(indeed, we''ve been compiling our own since the beginning, but
wouldn''t rails be a much friendlier install if we didn''t have
to?
Rails has always had a relatively low barrier to tinkering as one of
its greatest strengths--why not continue to improve this?)
Could a pure-ruby replacement to readline be built on os x? Could
libedit be used anyways (via some sort of c-wrapper, or otherwise)? At
the very least, could the areas with readline requirements right now
revert back to using stdin/stdout directly?
Licensing concerns will likely keep readline out of OS X for a long
time. I doubt that they''ll fix this bug soon. Is libedit really so
deficient that it can''t be made to work?
Brian
On 4/26/05, Lon Baker <lon-JCsVN+o+Xp98UrSeD/g0lQ@public.gmane.org>
wrote:> Marc,
>
> I have been working with Rails, Ruby, MySQL 4.1.x on Tiger for about
> a month.
>
> The main issue I had to overcome is that Apple''s version of Ruby
> doesn''t include the readline library. This is caused by the
inclusion
> of libedit, an alternative to readline, in the /usr/lib directory.
> Unfortunately the Ruby source does not compile against this library
> since it requires readline and not libedit. Apple''s solution was
to
> disable the Ruby readline extension in their version of Ruby.
>
> My solution was to install readline in /usr/local/lib and create a
> link in /usr/lib. This allows you to compile a fully functional
> version of Ruby in /usr/local, then remove/deactivate Apple''s
version
> of Ruby. From my limited understanding if you just install readline
> in /usr/local/lib, configuring the Ruby source will find the libedit
> library in /usr/lib first and fail to compile the readline extension.
>
> The one wrinkle I hit with Readline 5.0 was that it incorrectly sets
> the LDFLAG (I think) to "-dynamic" instead of
"-dynamiclib" when you
> try and compile it. This is fixed by running ./configure, then
> manually adjusting the Makefile in the "shlib" directory before
> compiling.
>
> All the other usual issues with database compatibility apply on Tiger
> the same as Panther, such as MySQL 4.1.x vs. 4.0 password hashing. I
> have not tried using Apple''s version of SQLite that is now
included.
>
> I have reported the lack of readline support in Ruby to Apple (Bug
> Reporter #4039716), they classified it as a "Serious Bug", and as
of
> today the report is still marked as Open.
>
> --
> Lon Baker
>
> Speedymac LLC
> http://www.speedymac.com
> AIM: spdemac
> Skype: spdemac
>
> On Apr 26, 2005, at 5:28 PM, Marc Kohlbrugge wrote:
>
> > Hi,
> >
> > In some mailing-list I saw you were wondering if other people were
> > playing with the rails + tiger -combo. Well, I try to.. I get rails
> > to work but got some weird errors when trying to use databases.
> >
> > So I know how to set up Rails on tiger, but it doesn''t fully
work.
> > If you want to try it, just mail me and I will try to make some
> > howto or something.
> >
> > But if it''s already working for you, including databases and
> > stuff.. could you give me a howto?
> >
> > Let me know.
> >
> > Regards,
> > Marc
> >
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
--
The years ahead pick up their dark bags.
They move closer. There''s a slight rise in the silence
then nothing.
--
(If you''re receiving this in response to mail sent to
bluczkie-OM76b2Iv3yLQjUSlxSEPGw@public.gmane.org, don''t be concerned
This is my new address,
but mail will be forwarded here indefinitely)