`cabal run` creates `dist-newstyle/cache/compiler` in the current folder

[Bodigrim]

Describe the bug
Running a standalone script (#!/usr/bin/env cabal) creates and leaves dist-newstyle/cache/compiler in the current folder. This is a regression in comparison to Cabal 3.14.1.0.

To Reproduce
Steps to reproduce the behavior:

$ ll dist-newstyle/cache/compiler; echo '#!/usr/bin/env cabal\n{- cabal:\nbuild-depends: base\n-}\nmain :: IO ()\nmain = pure ()' > Main.hs && chmod +x Main.hs && ./Main.hs && ll dist-newstyle/cache/compiler
ls: dist-newstyle/cache/compiler: No such file or directory
-rw-r--r--  1 andrew  staff  25365 Dec 29 01:31 dist-newstyle/cache/compiler

Expected behavior
With Cabal 3.14.1.0 no files are created in the current folder.

System information

• macOS, GHC 9.6.6, Cabal HEAD built from 4b2e5f0

[Bodigrim]

IMHO this is a fairly grave regression, rendering Cabal scripts unusable. Could someone please reproduce and triage?

[ffaf1]

I confirm I can reproduce it.

If I modify the .hs and dist-newstyle is already present, I get a build/ folder too.

f@x270:/tmp/prova$ ls
build  dist-newstyle  Main.hs

[ffaf1]

c89ab54 #10254

@alt-romes does this ring a bell?

[alt-romes]

c89ab54 #10254

@alt-romes does this ring a bell?

It does not, sorry. Do you think the commit you referenced is related to this regression? Why?

[alt-romes]

Ah, actually some of those lines could be culpable for this:

c89ab54#diff-2adae381a2eb2d8c804d5396694a431e1e3babd816a5d2408a62213cf774a893L388-L398

The call to createDirectory was there before too, but it was not necessarily invoked (it depends on what initprojectskeleton did with it.

[ffaf1]

@alt-romes it definitely looks like it could be related to the problem.
I just did a git bisect and landed on that commit.

Are you working on it? If you need an additional pair of eyes to diagonse this, I can gladly help!

[alt-romes]

I'll take a look today.