-
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 new-path #4661
Comments
How does this relate/complement/interact/differ from #2771? (or why can't the functionality be provided by e.g. |
Check out #4220 too! |
Wow #4220 looks pretty much like this. #2771 looks also quite usable. I just don't think that bolting the path logic into the show-build-info is a good idea, that just hides it at an obscure location. However, had I known of #2771, I might now have ended up implementing |
@angerman btw, implementing |
See also #3850. |
I find myself often needing paths for cabals new-build artifacts. stack has a
path
command, that allows to retrieve information about directories for the current setup.A
cabal new-path
command providing similar functionality would be quite useful.E.g.
cabal new-path --dist-dir
would provide the directory that used to bedist
for the current target. E.g. the one thatcabal new-build
would build by default.This could of course be discriminated by target.
The text was updated successfully, but these errors were encountered: