Cons 2.3 Command dependencies broken?

[Steven Allen]

I downloaded the beta version of 2.3 a week or so ago (finally), and after
some head scratching I discovered a bug in it (I think).  I couldn't find
any documentation saying this had changed, and it works fine in 2.2 so I'm
assuming it's a 2.3 bug (since it almost works).   

I'm emailing to the list in hopes that someone else has already fixed
this....

Basically, the "Command" targets can't be a hash/list or dependencies are
not calculated correctly.  I.E. in 2.2 and 2.3 this works fine, as expected:

  Command $env "foo.3", "foo.2", "cat foo.2 > foo.3";
  Command $env "foo.2", "foo.1", "cat foo.1 > foo.2";

Any combination of changing foo.1 or foo.2 or foo.3 works as it should.

However this works as expected (i.e. the same as above) in cons 2.2 but NOT
2.3.

  Command $env ["foo.3"], "foo.2", "cat foo.2 > foo.3";
  Command $env ["foo.2"], "foo.1", "cat foo.1 > foo.2";

I.E change foo.1 and only foo.2 changes.  A second run of cons is required
in order to update foo.3.

And yes, adding a Depends command fixes this, but how ugly is that given
there's already a clear dependency list here  (the arguments to the
"Command" command).

If you want the test files I used to prove this to myself, email me and I'll
be happy to send them to you...

Steve Allen