It seems like it should be a separate environmental thing though. I would have the rakefile itself define HOME based on USERPROFILE if it doesn't exist then. I'd rather not see something like that put into the specs themselves.
On Mon, Jun 30, 2008 at 11:16 AM, Peter Bacon Darwin < [EMAIL PROTECTED]> wrote: > That only works for IronRuby but not for running the Rakefile under > CRuby. > > Pete > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Michael Letterle > *Sent:* Monday,30 June 30, 2008 16:04 > *To:* [email protected] > *Subject:* Re: [Ironruby-core] HOME env variable required > > > > Or add the HOME logic to irvars.bat > > On Mon, Jun 30, 2008 at 10:31 AM, John Lam (IRONRUBY) <[EMAIL PROTECTED]> > wrote: > > Peter Bacon Darwin: > > > > How conventional in the Ruby World in general is it to expect the HOME > > variable to exist? > > Wouldn't it be easier to have a check at the start of the RakeFile and > > spec_runner.rb that creates the HOME variable (from USERPROFILE, etc) > > if it is nil? Then you don't need to go and hack the specs themselves. > > In the new world, we'll likely have to modify the mspec spec runner and > contribute the changes back to the mspec project. specrunner.rb and friends > are effectively deprecated today. > > Thanks, > -John > > > > _______________________________________________ > Ironruby-core mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ironruby-core > > > > > -- > Michael Letterle > [Polymath Prokrammer] > http://blog.prokrams.com > > _______________________________________________ > Ironruby-core mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/ironruby-core > > -- Michael Letterle [Polymath Prokrammer] http://blog.prokrams.com
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
