Not yet for screened, but please take a look and tell me what you think.

1 patch for repository https://darcs.net/screened:

patch c755a7925a3509ccc2b92ab51ce3e4870a2a572d
Author: Ben Franksen <ben.franksen@online.de>
Date:   Sun May 19 13:47:10 CEST 2024
  * make execution of release/gen-version-info.hs more robust

  Using cabal run instead of runghc inside of Setup.hs ensures that we use the
  same ghc version that cabal uses, avoiding dependency errors.

Attachments

• make-execution-of-release_gen_version_info_hs-more-robust.dpatch
• patch-preview.txt

What would happen if the user had passed `--with-compiler` to their
"outer" cabal invocation? I don't think we'd inherit it, would we?

Ha, that's precisely what prompted me to try this. I ran into this problem:

ben@home[1]:.../darcs/screened>cabal build -w ghc-9.6
Build profile: -w ghc-9.6.2 -O1
In order, the following will be built (use -v for more details):
 - darcs-2.19.1 (lib:darcs, exe:darcs, test:darcs-test) (first run)

/home/ben/src/darcs/screened/release/gen-version-info.hs:7:1: error:
    Could not load module ‘System.Process’
    It is a member of the hidden package ‘process-1.6.5.0’.
    Perhaps you need to add ‘process’ to the build-depends in your .cabal file.
    It is a member of the hidden package ‘process-1.6.20.0’.
    Perhaps you need to add ‘process’ to the build-depends in your .cabal file.
    It is a member of the hidden package ‘process-1.6.20.0’.
    Perhaps you need to add ‘process’ to the build-depends in your .cabal file.
    Use -v to see a list of the files searched for.
  |
7 | import System.Process ( readProcess )
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
callProcess: cabal "run" "./release/gen-version-info.hs" (exit 1): failed
Error: cabal: Failed to build darcs-2.19.1.

But with this patch applied it worked.

This may have been after I manually deleted some of the ~/.cabal/store 
subdirectories, so perhaps not easily reproducable.

Interesting. Maybe it's passing on state via environment variables?

Anyway, no objections if it makes things better. Hopefully longer-term
we can replace it with hooks.

Self-accepting this one so it can go into 2.18.3. It has repeatedly 
proved useful (at least to me) and works with both stack and cabal.