-
Notifications
You must be signed in to change notification settings - Fork 691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cabal init --overwrite: openFile: app/Main.hs: does not exist (No such file or directory) #8207
Comments
by the way, i found it surprising that cabal init --overwrite changes the working directory to |
It is, due to #7873. cabal/cabal-install/main/Main.hs Line 921 in 87bfc00
|
Adding a message would be quite easy, since this is desirable behavior that just needs some information attached. @ptkato do you want to add the PR for that or should I? Additionally, I notice the log outputs are fucked up for |
That message stuff doesn't seem right, it is already like that, kinda: cabal/cabal-install/src/Distribution/Client/Init/Types.hs Lines 360 to 362 in 5a8e997
|
Yeah, i thought i updated that already and assumed there was something different for |
@emilypi you're right, I mixed up my binaries. the spacing is fine, but the error is still there:
|
There are a few weird behaviours at play here. I remember discussing about allowing only 1 backup at a given time, instead of having multiple of them, for example if we run Also, the overwriting does not like when used in conjunction with the "new project directory" feature from #7873, it writes the new files into the backed up directory, instead of the new one, due to how the backing up works. Should we disallow the usage of the directory extra argument with overwrite, or should we do something else? |
All in all, the backup feature is being a bit disruptive considering all the rest, I propose that we move that functionality from within the inner bowels of the Any objections? What are your thoughts? |
Describe the bug
cabal init --overwrite: openFile: app/Main.hs: does not exist (No such file or directory)
To Reproduce
Steps to reproduce the behavior:
Please use version-prefixed commands (e.g.
v2-build
orv1-build
) to avoid ambiguity.Expected behavior
no error, the existing .cabal file is overwritten
System information
cc @emilypi @ptkato
The text was updated successfully, but these errors were encountered: