Stephen Sherratt
Stephen Sherratt
> How would you expect dune fmt to work? I'm not super familiar with how it works currently, but I would have thought the only thing that needs to change...
Note that Opam doesn't currently solve this problem. On my NixOS machine I cannot install `core` with Opam: ``` #=== ERROR while compiling bin_prot.v0.17.0 ===================================# # context 2.3.0 | linux/x86_64...
> I would suggest that it prints a warning. If the shebang is wrong, it should be corrected in some ways and people should be aware that we try to...
Good point @Leonidas-from-XIV. Ok rather than automatically fixing the problem, let's just print a warning when dune fails to execute a script with a suspect shebang. Best case scenario this...
(I changed the description of this issue to be about printing a message rather than automatically fixing the problem.)
@kayodegigz it would be nice if we could avoid changing anything inside src/dune_engine as changes inside that module require extra scrutiny and reviews tend to take much longer. Looking closer...
I haven't seen this issue in over a year so there's a good chance it's been fixed accidentally. Optimistically closing.
I understand why this happens. Dune currently only records depexts into lockfiles for platforms that it solves for rather than all the platforms listed in the opam file. I think...
The problem this reproduces is now fixed. Closing.
@kemsguy7 I have unassigned you from your original issue, but before I assign you to this issue I'd like to see a proposal of which small component of this issue...