On Oct 27, 2:21 pm, Bil K. [email protected] wrote:
John J. wrote:
On Oct 27, 2007, at 11:03 AM, Richard K. wrote:
Realize they could have totally screwed this up by reordering the
above load paths, but Laurent is a smart guy
+1
(Havenāt seen Richās original show up in comp.lang.ruby yet.)
Me neither. Possibly an HTML post eaten by the gateway?
John J. wrote:
On Oct 27, 2007, at 11:03 AM, Richard K. wrote:
Realize they could have totally screwed this up by reordering the
above load paths, but Laurent is a smart guy
+1
(Havenāt seen Richās original show up in comp.lang.ruby yet.)
Later,
On Oct 27, 2007, at 2:15 PM, Brian A. wrote:
(Havenāt seen Richās original show up in comp.lang.ruby yet.)
Me neither. Possibly an HTML post eaten by the gateway?
Yes:
Content-Type: multipart/alternative; boundary=Apple-Mail-18-445454026
James Edward G. II
From: āJames Edward G. IIā [email protected]
Thatās because it originated on the mailing list side. The gateway
then submitted it to our Usenet host and they declined it, so it
never hit comp.lang.ruby.
Iām sure this has been asked before, so apologies for what is
almost surely a repeat question, but ā¦
Would it be reasonable to just convert all messages to text-only
before submitting them to the Usenet host?
Another mailing list Iām on works that way, and it seems pretty
reasonable. If it modifies a message, it just appends a note,
like ānon-text attachments strippedā or such.
Essentially, Iām wondering if the situation is,
Thanks,
Bill
Hi ā
On Sun, 28 Oct 2007, James Edward G. II wrote:
+1
(Havenāt seen Richās original show up in comp.lang.ruby yet.)
Me neither. Possibly an HTML post eaten by the gateway?
Yes:
Content-Type: multipart/alternative; boundary=Apple-Mail-18-445454026
I received it; itās ruby-talk: 276132.
David
On 10/28/07, James Edward G. II [email protected] wrote:
On Oct 27, 2007, at 5:11 PM, Ben M. wrote:
Is Apple going to be maintaining it so it stays current with the
latest version of ruby?
Yes, Iām very curious about this point as well. Itāll be terrific if
they can bump it to 1.8.6p110 in an early bug fix patch. Thatās what
Iām hoping we gain out of this framework setup.
We will provide updates, if the bugs they fix are important enough.
Security issues will also be fixed the soonest possible.
The version in Leopard is 1.8.6 p 36 + the security fixes that were
included in p110. p110 was unfortunately released a bit too late for
us.
Laurent
On 10/28/07, James Edward G. II [email protected] wrote:
On Oct 27, 2007, at 5:07 PM, Pat M. wrote:
Are there any compelling reasons to use the built-in install? I was
just planning on using macports cause it works so well.
I think the built-in install will be great for deploying RubyCocoa
applications. You can count on it being there on other machines for
that purpose.
The built-in version also provides DTrace support.
Laurent
Are there any compelling reasons to use the built-in install? I was
just planning on using macports cause it works so well.
Pat
Pat M. wrote:
Are there any compelling reasons to use the built-in install? I was
just planning on using macports cause it works so well.
Pat
I am wondering the same thingā¦ I currently compile from source but
would gladly switch to the built-in install if it is going to be kept up
to date. Is Apple going to be maintaining it so it stays current with
the latest version of ruby?
-Ben
On Oct 27, 2007, at 5:07 PM, Pat M. wrote:
Are there any compelling reasons to use the built-in install? I was
just planning on using macports cause it works so well.
I think the built-in install will be great for deploying RubyCocoa
applications. You can count on it being there on other machines for
that purpose.
James Edward G. II
On Oct 27, 2007, at 3:31 PM, David A. Black wrote:
above load paths, but Laurent is a smart guy
+1
(Havenāt seen Richās original show up in comp.lang.ruby yet.)
Me neither. Possibly an HTML post eaten by the gateway?
Yes:
Content-Type: multipart/alternative; boundary=Apple-
Mail-18-445454026
I received it; itās ruby-talk: 276132.
Thatās because it originated on the mailing list side. The gateway
then submitted it to our Usenet host and they declined it, so it
never hit comp.lang.ruby.
James Edward G. II
Pat M. wrote:
Are there any compelling reasons to use the built-in install? I was
just planning on using macports cause it works so well.
Pat
The question I havenāt seen asked (or answered) is how would I switch
from my /usr/local version of Ruby & Rails (and gems) to the Leopard
stock versions? I canāt just pluck /usr/local/bin out of my PATH,
because there are other things installed there (ImageMagick, Subversion
[well, thatās now system installed though], etc.) ?
Do I just delete/rename the applications? (ruby, irb, rake, svn*, etc)
On 10/28/07, John T. [email protected] wrote:
[well, thatās now system installed though], etc.) ?
Do I just delete/rename the applications? (ruby, irb, rake, svn*, etc)
you can append /usr/local to the end of your PATH instead. if /usr/bin
is before /usr/local/bin in your PATH ENV then /usr/bin/whatever will
be found/used first.
Iād consider cleaning up your source_cache as well, and removing
~/.ruby_inline.
Also there is an issue with the compiler flags set using RubyInline
that you will want to fix.
I wrote a sed script to do it. Very helpful if you need to fix it on
multiple machines.
sudo sed -i -e ā387,1s/flags\ =\ @flags.join('\ ')/&\ +\ '
-lruby'/ā
/usr/lib/ruby/user-gems/1.8/gems/RubyInline-3.6.4/lib/inline.rb
On Oct 27, 2007, at 5:11 PM, Ben M. wrote:
Is Apple going to be maintaining it so it stays current with the
latest version of ruby?
Yes, Iām very curious about this point as well. Itāll be terrific if
they can bump it to 1.8.6p110 in an early bug fix patch. Thatās what
Iām hoping we gain out of this framework setup.
James Edward G. II
Michael S. wrote:
On 10/28/07, John T. [email protected] wrote:
[well, thatās now system installed though], etc.) ?
Do I just delete/rename the applications? (ruby, irb, rake, svn*, etc)
you can append /usr/local to the end of your PATH instead. if /usr/bin
is before /usr/local/bin in your PATH ENV then /usr/bin/whatever will
be found/used first.
Iād consider cleaning up your source_cache as well, and removing
~/.ruby_inline.
Also there is an issue with the compiler flags set using RubyInline
that you will want to fix.
I wrote a sed script to do it. Very helpful if you need to fix it on
multiple machines.
sudo sed -i -e ā387,1s/flags\ =\ @flags.join('\ ')/&\ +\ '
-lruby'/ā
/usr/lib/ruby/user-gems/1.8/gems/RubyInline-3.6.4/lib/inline.rb
Oh yeah! Didnāt even think of that!
I donāt seem to have a ~/.ruby_inline file (I installed using the
Hivelogic directions, from source), so not sure if I need to do that.
My source_cache is in the (now unused) /usr/local path, do I need to
worry about it?
Thanks!
On 27/10/2007, Laurent S. [email protected] wrote:
We will provide updates, if the bugs they fix are important enough.
Security issues will also be fixed the soonest possible.
When you say āprovide updatesā can I just check that you do mean via
the Apple Software Update system?
Regards,
Matt.
John T. wrote:
Michael S. wrote:
On 10/28/07, John T. [email protected] wrote:
[well, thatās now system installed though], etc.) ?
Do I just delete/rename the applications? (ruby, irb, rake, svn*, etc)
you can append /usr/local to the end of your PATH instead. if /usr/bin
is before /usr/local/bin in your PATH ENV then /usr/bin/whatever will
be found/used first.
ā¦
Oh yeah! Didnāt even think of that!
I donāt seem to have a ~/.ruby_inline file (I installed using the
Hivelogic directions, from source), so not sure if I need to do that.
My source_cache is in the (now unused) /usr/local path, do I need to
worry about it?
Thanks!
Hmmā¦ I made that change, then tried to update gems (sudo gem update).
It seemed to be going well, until it hit this and died:
Installing ri documentation for activerecord-1.15.5ā¦
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rdoc/rdoc.rb:101:in
`errorā: (RDoc::RDocError)
Directory /Library/Ruby/Gems/1.8/doc/activerecord-1.15.5/ri already
exists, but it looks like it
isnāt an RDoc directory. Because RDoc doesnāt want to risk
destroying any of your existing files, youāll need to
specify a different output directory name (using the
āop option).
On Oct 27, 2007, at 5:59 PM, Bill K. wrote:
I received it; itās ruby-talk: 276132.
Thatās because it originated on the mailing list side. The
gateway then submitted it to our Usenet host and they declined
it, so it never hit comp.lang.ruby.
Iām sure this has been asked before, so apologies for what is
almost surely a repeat question, but ā¦
Itās been asked, yes. We went over it again recently. See the
thread āIs there a standard pattern for threaded access to a file?ā
which we sort-of hijacked for a gateway discussion.
Would it be reasonable to just convert all messages to text-only
before submitting them to the Usenet host?
Mostly, yes.
Essentially, Iām wondering if the situation is,
- yes we could convert messages if someone volunteers code to do so
This is pretty much it. I made the gateway code public some time ago
to support people hacking on it:
http://blog.grayproductions.net/categories/the_gateway
No one has stepped up yet.
To be fair, I think some are waiting on the TMail-based rewrite Iāve
promised in the past. Iāve worked on it a bit, but just havenāt
finished it yet. Iāll spend some time on it today and see how close
I can get itā¦
James Edward G. II
John T. wrote:
The question I havenāt seen asked (or answered) is how would I switch
from my /usr/local version of Ruby & Rails (and gems) to the Leopard
stock versions? I canāt just pluck /usr/local/bin out of my PATH,
because there are other things installed there (ImageMagick, Subversion
[well, thatās now system installed though], etc.) ?
Do I just delete/rename the applications? (ruby, irb, rake, svn*, etc)
If you want to keep using your locally installed commands from
/usr/local/*, but switch back and forth between you custom version of
ruby and the system-provided one, then Iād recommend installing it under
a custom prefix (i.e. not /usr/local), and add/remove that path from
your PATH. At least thatās what I would try to do - or play around with
symlinks. However, the PATH method can be switched at will on a
per-process basis, while using symlinks would affect the whole system at
once.
mortee
On Oct 30, 10:10 am, āLaurent S.ā
[email protected] wrote:
We received many valuable feedback during the past days, thank you
very much! We also received lots of pertinent questions, and since
most of them were asked many times, we decided to open a FAQ:
http://trac.macosforge.org/projects/ruby/wiki/FAQ
Thank you for all of the great work, and the FAQ. However, thereās one
question I have that I didnāt see answered.
The āWhatās newā page states:
Ruby libraries or extensions that you install manually, will go in
/Library/Ruby/Site/1.8, which is empty after the installation, but
part of the default Ruby load path before others. You can therefore
install any Ruby library or extension without worrying about
incidentally modifying things in /System.
My question is, what about ruby applications that I install
manually? That is, a ruby package that contains a main executable
script, which currently goes into /usr/local/bin when I pass āā
prefix=/usr/localā into the āsetup.rb configā command that I use
during installation? Where will the executable script go by default
under Leopard? Will it go into /usr/bin?
Right now, I only have a single such program installed and which I
rely on, which is misen (http://devel.korinkan.co.jp/misen/). When I
upgrade to Leopard, I was thinking of removing my entire custom ruby
installation from /usr/local, and relying on the built in one. But
what will happen if I try to install misen?