I don't know how relevant folks will consider this, but I've
been working on ways to use Cucumber to test SketchUp plugins.
Some of the same tricks might be relevant to MacRuby apps...
Using Cucumber with SketchUp
http://www.cfcl.com/rdm/weblog/archives/001714.html
-r
--
http://www.cfcl.com/
Matt, you are correct because I'm seeing 9 failures at this time.
-Conrad
On Mon, Nov 2, 2009 at 12:55 PM, Matt Aimonetti wrote:
> Just FYI, I found one of the major issue with macruby + rspec, the problem
> being that rspec relies on Kernel.caller and MacRuby's version isn't fully
> compatible
Just FYI, I found one of the major issue with macruby + rspec, the problem
being that rspec relies on Kernel.caller and MacRuby's version isn't fully
compatible with C Ruby's.
Anyone knows of rspec matchers for bacon?
- Matt
On Mon, Nov 2, 2009 at 11:37 AM, John Barnette wrote:
> Hey,
>
> On Mo
Hey,
On Mon, Nov 2, 2009 at 12:06 AM, Eloy Duran wrote:
> I think the best solution would be if RubyGems would apply the same program
> prefix or suffix to the executables it installs. So in the case of MacRuby,
> the executable would be: /usr/bin/macspec.
> I haven't had the time to look at Ruby
On Mon, Nov 2, 2009 at 2:46 AM, Eloy Duran wrote:
> Hey Conrad,
>
> Hi Eloy, I have spent a bit of time with it. Here's what I did to get
> things going:
>
> 1) sudo gem install rvm
>
> 2) add the following to your .profile after the last 'export PATH='
> setting:
>
> if [ -s ~/.rvm/scri
Hey Conrad,
Hi Eloy, I have spent a bit of time with it. Here's what I did to
get things going:
1) sudo gem install rvm
2) add the following to your .profile after the last 'export PATH='
setting:
if [ -s ~/.rvm/scripts/rvm ] ; then source ~/.rvm/scripts/
rvm ; fi
Note:
Hi Eloy, I have spent a bit of time with it. Here's what I did to get
things going:
1) sudo gem install rvm
2) add the following to your .profile after the last 'export PATH='
setting:
if [ -s ~/.rvm/scripts/rvm ] ; then source ~/.rvm/scripts/rvm ; fi
Note: I didn't like running
Hey Conrad,
I agree that you don't notice the issue if you use RVM. But the fact
remains that the issue still exists…
So as an interim solution you can indeed use RVM or, like Laurent
does, use a separate gem home, but on the long run, imo, RubyGems
should be enhanced to take care of this
Hi ALL, it's not too much of an issue if one is using the Ruby Version
Manager (RVM) because it creates separate executable and gem directories for
each Ruby implementation. I haven't used MacRuby under RVM but it seems to
do an excellent job of adding the appropriate executables to the path based
That would probably be the best solution in the interim.
I personally install all of my MacRuby gems in ~/.gem/macruby/1.9.0
(which is the default directory if you don't run macgem under sudo).
This way /usr/bin is not altered and when I want to run a MacRuby gem
helper I simply append ~/.g
I think the best solution would be if RubyGems would apply the same
program prefix or suffix to the executables it installs. So in the
case of MacRuby, the executable would be: /usr/bin/macspec.
I haven't had the time to look at RubyGems yet though, if anyone wants
to take a stab at fixing
On Nov 1, 2009, at 10:52 PM, s.ross wrote:
I'm not sure what a sensible solution is to this, but thought since
rSpec is getting some attention, I'd bring this up.
You can always override the shebang line by running a script directly
with ruby (it's not a coincidence that the shebang line is
Unfortunately this is not an issue with MacRuby, you would have many issues
with ruby1.9 or any other implementations.
- Matt
On Sun, Nov 1, 2009 at 10:52 PM, s.ross wrote:
> When installing the gem using macgem, a shebang line is written pointing to
> macruby. The "spec" binary copied into /us
13 matches
Mail list logo
