<div dir="ltr">Sure... if you want to do stuff like:<br><br>require File.expand_path(File.join(File.dirname(__FILE__), "..", "spec_helper")))<br><br>This is super-unDRY and I'd like to be able to have this happen automatically without having to do spec -O spec/spec.opts ...<br>
<br>Is there a reason not to try and find spec/spec.opts and load it automatically?<br><br>-- Yehuda<br><br><div class="gmail_quote">On Mon, Aug 25, 2008 at 12:22 PM, Pat Maddox <span dir="ltr"><<a href="mailto:pergesu@gmail.com">pergesu@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Mon, Aug 25, 2008 at 2:41 PM, Yehuda Katz <<a href="mailto:wycats@gmail.com">wycats@gmail.com</a>> wrote:<br>
> I spoke to dchelimsky this morning and am bringing our conversation to the<br>
> list.<br>
><br>
> Effectively, I asked why we don't automatically require spec/spec.opts<br>
> (which I wanted in order to be able to yank require 'spec_helper' from my<br>
> specs, because require 'spec_helper' and require '../spec_helper' results in<br>
> two requires, which sucks).<br>
<br>
</div>Doesn't File.expand_path solve this issue?<br>
<br>
Pat<br>
_______________________________________________<br>
rspec-devel mailing list<br>
<a href="mailto:rspec-devel@rubyforge.org">rspec-devel@rubyforge.org</a><br>
<a href="http://rubyforge.org/mailman/listinfo/rspec-devel" target="_blank">http://rubyforge.org/mailman/listinfo/rspec-devel</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Yehuda Katz<br>Developer | Engine Yard<br>(ph) 718.877.1325<br>
</div>