Unexpected behavior for `spack develop --force`

[Alex Richert]

Steps to reproduce

$ . share/spack/setup-env.sh
$ spack env create testenv
$ spack env activate testenv
$ spack develop gmake@4.4.1 # package doesn't matter
$ spack develop --clone gmake@4.4.1
==> Error: Path /dev/shm/spack/var/spack/environments/testenv/gmake already exists and cannot be cloned to. Use `spack develop -f` to overwrite.
$ spack develop --clone --force gmake@4.4.1
==> Skipping developer download of gmake@=4.4.1 because its path already exists.
$ spack develop --force gmake@4.4.1
==> Skipping developer download of gmake@=4.4.1 because its path already exists.

Error message

See above. The --force option does not seem to have any effect, other than turning an error to a 'Skipping' notification.

Information on your system

• Spack: 0.22.0.dev0 (62554ce)
• Python: 3.6.8
• Platform: linux-centos8-zen3
• Concretizer: clingo

General information

• I have run spack debug report and reported the version of Spack/Python/Platform
• I have searched the issues of this repo and believe this is not a duplicate
• I have run the failing commands in debug mode and reported the output

[Massimiliano Culpo]

Confirmed