@becker33 it would be cool to extend this functionality a little to allow someone to clone a named environment -> to an independent environment in a directory like so,

$ spack env create /path/to/new/environment myoldenv

@alecbcs that is already covered by this PR

Trying this PR I ran into a couple of errors on edge cases. Happy to help work on fixing these if needed.

While the following works when creating a new environment,

> spack env create .
==> Created independent environment in: /Users/scott112/src/scratch/spack-test
==> Activate with: spack env activate .

I noticed that if you attempt to do the same while cloning an existing environment it fails,

> spack env create . default
==> Error: [Errno 17] File exists: '.'

If you point to a nonexistent directory it appears to then work, but fails to generate the view.
(I think this is because the clone is copying the existing view from the other environment.)

> spack env create ./spack-env-test default
==> Created independent environment in: /path/to/spack-env-test
==> Activate with: spack env activate ./spack-env-test
==> Error: Failed to generate environment view, because the target /path/to/spack-env-test/.spack-env/._view/52zrqd743mpt4bo2evttasinwfeji2zl already exists or is not empty. To update the view, remove this path, and run `spack env view regenerate`

I think it's more accurate to say it emits an error about the view -- you're right that the problem is that the view already exists.

No need for the label, was merged before we branched