Cabal arogently assumes names shouldn't collide with those already on Hackage

[TomMD]

Describe the bug

$ cabal init
cabal: The name ____ is already in use by another package on Hackage.

But lots of people use Haskell and cabal outside of the context of what is on Hackage or while building software never intended to be uploaded to hackage. There is no reason to use the entire haskell package set as a deny list.

To Reproduce

mkdir <some name on hackage>
cd $REALLY_COMMON_TERM
cabal init

Expected behavior
Cabal init happens
.

[gbaz]

dup of #7273 but despite that issue being closed it still doesn't seem resolved, sigh.

[gbaz]

(ah, i see, the fix there was to make the error more informative, this issue is whether the behavior is desired at all or not)

[TomMD]

How about a "force" flag?

[Mikolaj]

Hi! It works fine on master branch (to be released as 3.8; I haven't tried with 3.6.2). It asks you whether you want to name the package so anyway and then proceeds fine. Please confirm.

[Mikolaj]

@TomMD: were you able to confirm your problem is solved on master branch?

[TomMD]

Yes. I can verify 3.6.2 does not work but HEAD does for me. Thanks!

[Mikolaj]

@TomMD: thank you!

[damienstanton]

I'd second a --force option. This constraint feels like it is in the wrong place; It should be an error at package publish time, not package creation time.

[Mikolaj]

@damienstanton: hi! do you refer to the behaviour on master branch? If so, could you elaborate how you'd like to change it?

[damienstanton]

@damienstanton: hi! do you refer to the behaviour on master branch? If so, could you elaborate how you'd like to change it?

No it appears that master does not have this issue, thanks!

[Mikolaj]

@damienstanton: thank you for confirming.