Ed Page bb1f6f29bc fix(embedded): Don't pollute script dir with lockfile ... This puts the lockfile back into a target directory in the users home, like before #12268. Another idea that came up was to move the workspace root to be in the target directory (which would effectively be like pre-#12268) but I think that is a bit hacky / misleading. This does mean that the lockfile is buried away from the user and they can't pass it along with their script. In most cases I've dealt with, this would be fine. When the lockfile is needed, they will also most likely have a workspace, so it shoud have a local lockfile in that case. The inbetween case is something that needs further evaluation for whether we should handle it and how.		2023-06-17 15:27:03 -05:00
..
build-std	Add requirements to cargo_test.	2022-07-30 19:36:58 -07:00
testsuite	fix(embedded): Don't pollute script dir with lockfile	2023-06-17 15:27:03 -05:00