not possible to specify a custom pakefile.php in random directory

[gggeek]

The code will only look for pakefile.php in current dir and parent dirs.
It is possible to pass a "pakefile" option, but if that pakefile is in an unrelated dir path, it will not be used.
(Note: tested on windows)

[indeyets]

I'm testing on OS X and everything looks fine. can you give me exact example?

test 1: looks ok

cd ..
./pake/bin/pake -f pake/pakefile.php -T

   # using local version of pake. good!
available pake tasks:
  …

test 2: looks ok

cd ../blog
../pake/bin/pake -f ../pake/pakefile.php -T
   # using local version of pake. good!
available pake tasks:
  …

[gggeek]

It seems that the way you specify the location for pakefile.php has an impact: if specified as relative to current dir is ok. If specified as absolute path, not so much.

d:\htdocs\pake_gg>cd ..\test

d:\htdocs\test>php ..\pake_gg\bin\pake -f ..\pake_gg\pakefile.php --tasks
   # using local version of pake. good!
available pake tasks:
  ...

d:\htdocs\test>php ..\pake_gg\bin\pake -f D:\htdocs\pake_gg\pakefile.php --tasks

  [pakeException]
  No pakefile found (looking for: D:\htdocs\pake_gg\pakefile.php)

d:\htdocs\test>php ..\pake_gg\bin\pake -f \htdocs\pake_gg\pakefile.php --tasks
   # oops窶ｦ you're using installed pake. restarting with local version窶ｦ

[indeyets]

thank you! I can't reproduce is on osx, but at least I know where to look

[indeyets]

@gggeek I just committed something which might be a fix. can you check git-master please?

[indeyets]

@gggeek ping? does it work for you now?