make_sandbox won't accept path argument

I'm trying out MySQL Sandbox, and I get an error that looks like this:

$ make_sandbox 5.x.y $(pwd)/mysql-5.x.y-m5-osx10.5-x86_64.tar.gz
Executing low_level_make_sandbox --basedir=/Users/jrussell/opt/mysql/5.x.y \
 --sandbox_directory=msb_5_x_y \
 --install_version=5.x \
 --sandbox_port=5x0y \
 --no_ver_after_name \
 /Users/jrussell/desktop/sandbox/MySQL-Sandbox-3.0.17/mysql-5.x.y-m5-osx10.5-x86_64.tar.gz \
 --my_clause=log-error=msandbox.err
unexpected arguments </Users/jrussell/desktop/sandbox/MySQL-Sandbox-3.0.17/mysql-5.x.y-m5-osx10.5-x86_64.tar.gz>

(All the x's and y's above are real digits, I substituted letters in this output because x > 5. :-)

I also tried calling low_level_make_sandbox directly with these same parameters, with the --my_clause before the path to the .tar.gz file, but that produced the same error. Is there some dependency on the .tar.gz filename that it won't work unless the name is in some precise format? Or does MySQL Sandbox only work for specific releases that only go up to 5.5?

---

I got the original command working, but after putting it aside from some time and trying a different variation, again I get baffling errors that don't seem to agree with the syntax message:

$ low_level_make_sandbox $(pwd)/mysql-5.6.3.tar.gz
unexpected arguments <.../path stuff.../mysql-5.6.3.tar.gz>

I'm trying to specify the port and directory to install a "labs" build in a special location. I've tried all combinations of -P <portnum>, -P=<portnum>, --sandbox_port <portnum>, --sandbox_port=<portnum>, etc. before and after the path to the tarball, but always this "unexpected arguments" error. The cookbook doesn't show an example using low_level_make_sandbox here:

http://search.cpan.org/~gmax/MySQL-Sandbox-3.0.17/lib/MySQL/Sandbox/Recipes.pm#Creating_a_single_sandbox_with_user-defined_port_and_directory

In fact the examples all around this section don't use the tarball path format at all. That would help a lot if such examples could be sprinkled throughout the cookbook. Could the syntax check in the script test whether the "unexpected argument" is the name of a tarball, and give some more precise advice in that case? E.g. "you can't specify both a version and a tarball" or "when tarball is specified, you must also specify the -xyz option".

Oh I think I see the issue, so I'll try to summarize here to save some searching in a few months when I forget and encounter the error again. :-) The cookbook for specifying port and directory shows an example "low_level_make_sandbox --help", which suggests to me I'll call low_level_make_sandbox directly to perform this task. low_level_sandbox --help shows the syntax with the tarball coming last. That's the syntax I can't make work at all. Then I try make_sandbox, assuming the tarball must come last there too. In fact, the make_sandbox --help message suggests that's the case:

usage: ./make_sandbox version [options] {VERSION|tarball_full_name}.

However, the only way I can avoid the error is to call make_sandbox with all the options _after_ the tarball path:

make_sandbox $(pwd)/mysql-5.6.3.tar.gz --sandbox_port=49152 --sandbox_directory=<dirname>

If it's intentional that the tarball has to come before the -- options, could the order of items reflect that in the syntax message for make_sandbox and low_level_make_sandbox?