Cabal is inconsistent: cabal check errors on git:// but cabal get is happy fetching these

[phadej]

See #10659

[ulysses4ever]

The problem with moving the error to cabal get is that the user can't do anything about a Hackage package that uses git:// and that the user wants to get. Whereas at cabal check time you presumably have control over the package description and can fix the issue.

[geekosaur]

Is it possible to warn and ask for confirmation?

[ffaf1]

Is it possible to warn and ask for confirmation?

It would break many check-against-all-of-hackage scripts I fear.

[phadej]

The problem with moving the error to ...

Do both

Whereas at cabal check time you

You don't. Some maintainer does, if they care.

It would break many check-against-all-of-hackage scripts I fear.

Offer a force flag. (c.f. git push)

[geekosaur]

And/or default to force if stdin or stdout isn't a tty.

[phadej]

It would break many check-against-all-of-hackage scripts I fear.

EDIT: cabal get -s may fail anyway, if there are no repository info, or it's incorrect/obsolete.

[phadej]

And/or default to force if stdin or stdout isn't a tty.

Then there should be a fag to make cabal get -s fail. Both are probably good to have, with default being less important then. But IMHO, if cabal check fails by default, so should cabal get -s.