-
Notifications
You must be signed in to change notification settings - Fork 710
Make cabal check
supports targets (was cabal check all/local packages in a project)
#6282
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
Comments
jonathanknowles
added a commit
to IntersectMBO/bech32
that referenced
this issue
Feb 17, 2020
Unfortunately, there is no `cabal check all`. See: haskell/cabal#6282 So we have to manually change directories before we can issue the `cabal check` command.
jonathanknowles
added a commit
to IntersectMBO/bech32
that referenced
this issue
Feb 17, 2020
Unfortunately, there is no `cabal check all`. See: haskell/cabal#6282 So we have to manually change directories before we can issue the `cabal check` command.
jonathanknowles
added a commit
to IntersectMBO/bech32
that referenced
this issue
Feb 18, 2020
Unfortunately, there is no `cabal check all`. See: haskell/cabal#6282 So we have to manually change directories before we can issue the `cabal check` command.
jonathanknowles
added a commit
to IntersectMBO/bech32
that referenced
this issue
Feb 18, 2020
Unfortunately, there is no `cabal check all`. See: haskell/cabal#6282 So we have to manually change directories before we can issue the `cabal check` command.
jonathanknowles
added a commit
to IntersectMBO/bech32
that referenced
this issue
Feb 18, 2020
Unfortunately, there is no `cabal check all`. See: haskell/cabal#6282 So we have to manually change directories before we can issue the `cabal check` command.
5 tasks
jonathanknowles
added a commit
to IntersectMBO/bech32
that referenced
this issue
Feb 19, 2020
Unfortunately, there is no `cabal check all`. See: haskell/cabal#6282 So we have to manually change directories before we can issue the `cabal check` command.
cabal check
supports targets (was cabal check all/local packages in a project)
@robrix i hope you dont mind i renamed the issue to note what would be the task to get what you ask originally |
@jneira Whatever you think is best! |
I have a rough working implementation, #8587 needs to be resolved first. |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a project with multiple (indeed, many) packages. I would like to
cabal check
them in CI in the same way that I build them, test them, generate their haddocks, etc., i.e. usingcabal <blah> all
. However,cabal check
doesn’t accept any arguments, and in fact requires me to be in the same directory as the .cabal file for the package i want to check.Likewise, from the root of my project, if I want to
cabal check
some specific package, I have to firstcd
to its directory, becausecabal check <local package name>
isn’t accepted.cd
somewhere in a project other than where the.cabal
file for the package you want to check lives.cabal check <package name>
The text was updated successfully, but these errors were encountered: