Ticket #681 (new defect)
cabal-install init should not overwrite files without good reason
| Reported by: | ezyang | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | cabal-install-0.16 |
| Component: | cabal-install tool | Version: | 1.8.0.2 |
| Severity: | normal | Keywords: | |
| Cc: | Difficulty: | unknown | |
| GHC Version: | Platform: |
Description
If you run "cabal init" in a directory with an already existing .cabal file, it will happily overwrite the old version without asking you. It should detect that a file exists and ask you before writing it out (or even prompting you for info). Alternatively, it could fill up it's defaults using the existing .cabal file.
Furthermore, if you pass -n for non-interactive mode, cabal can't ask whether or not the user wanted to overwrite, so probably adding a --force flag is in order.
Change History
Note: See
TracTickets for help on using
tickets.
