I'm also with Nathan.
Don't touch the built-in Ruby on OS X. Installing gems touches
directories that nothing but OS updates should touch. OS updates can
blow them away, and change your Ruby version. You can break RubyCocoa
apps that depend on the default Ruby setup.
Install either by hand
On 06/06/2009, at 9:04 AM, Bodaniel Jeanes wrote:
> I completely disagree. MacPorts has quite a lot of issues and in
> performance tests is slow compared to the apple supplied one. Apple
> did a lot of performance enhancements on the built in one as well as
> including some common frameworks
>
> since using macports I've been able to installing anything and everything
> and get it all running
without any problems.
Glad you got it working
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
or Rails O
On 06/06/2009, at 9:21 AM, Torm3nt wrote:
>
> Actually I'm with Nathan on this one - since using macports I've been
> able to installing anything and everything and get it all running
> without any problems.
I agree, ports ruby is easier to deal with.
> I think Nathan is right - and because th
Actually I'm with Nathan on this one - since using macports I've been
able to installing anything and everything and get it all running
without any problems. I think Nathan is right - and because there
isn't any real version of ruby or similar kept updated for bsd
systems, I think it's problematic
I completely disagree. MacPorts has quite a lot of issues and in performance
tests is slow compared to the apple supplied one. Apple did a lot of
performance enhancements on the built in one as well as including some
common frameworks out of the box already accessible, as well as custom ones
like R
Also 5000JPY for the pre-conference party.
Regarding the size, maybe they didn't expect such a spike? Im not sure
as to what it's been like previously, but I definitely know there is a
fair amount of interest this year than previously from people outside
of Japan. Also small conferences are much
On 05/06/2009, at 9:53 PM, Bodaniel Jeanes wrote:
> Installing Ruby with MacPorts always causes issues because you
> install gems on one install but then run things with the other etc...
Sounds like you've not set up your PATH correctly.
My experience - in direct contrast to yours - is that u
What are the errors? Got a stacktrace?
--
Pat
On 05/06/2009, at 7:37 AM, Torm3nt wrote:
>
> Back again guys. So installing macports.etc. got things going for
> webrat - however, running my spec tests individually now are creating
> additional errors because ruby/rubygems and other affiiliates
well the good thing about macports is just deleting the /opt directory will
undo anything if you royally screw it up.
I wish i had a spare os x machine to try out a new install. I don't know how
you are having issues ... i've never even had to think about it.
I'd suggest deleting the /opt director
libxml2 and libxslt2 - same issue as on the ubuntu boxes (which I
resolved at work very easily), but handled very differently on my os x
box. hehe. I'm more than open to advice for future installs =P
--
Kirk Bushell
http://www.kirkbushell.com
Follow me: http://twitter.com/kirkbushell
On Fri,
which libraries?
On Fri, Jun 5, 2009 at 10:00 PM, Torm3nt wrote:
>
> Bodaniel - I know for a fact I've done a couple of things wrong - but
> I couldn't get webrat to install without mac ports, as there were some
> libraries I needed that didn't come with the dev tools I installed.
>
>
> --
> Kir
Bodaniel - I know for a fact I've done a couple of things wrong - but
I couldn't get webrat to install without mac ports, as there were some
libraries I needed that didn't come with the dev tools I installed.
--
Kirk Bushell
http://www.kirkbushell.com
Follow me: http://twitter.com/kirkbushell
that makes no sense. I didn't even need to use macports. Installing Ruby
with MacPorts always causes issues because you install gems on one install
but then run things with the other etc...
I literally reinstalled OS X about a month ago and didn't even install
MacPorts until railscamp. I certainly
I had to - was having issues with libraries =\
--
Kirk Bushell
http://www.kirkbushell.com
Follow me: http://twitter.com/kirkbushell
On Fri, Jun 5, 2009 at 9:40 PM, Bodaniel Jeanes wrote:
> You didn't also install ruby with macports did you?
>
> On Fri, Jun 5, 2009 at 9:37 PM, Torm3nt wrote:
You didn't also install ruby with macports did you?
On Fri, Jun 5, 2009 at 9:37 PM, Torm3nt wrote:
>
> Back again guys. So installing macports.etc. got things going for
> webrat - however, running my spec tests individually now are creating
> additional errors because ruby/rubygems and other aff
Back again guys. So installing macports.etc. got things going for
webrat - however, running my spec tests individually now are creating
additional errors because ruby/rubygems and other affiiliates
libraries are no longer using each other. Any ideas how to resolve
this?
--
Kirk Bushell
http://ww
17 matches
Mail list logo
