-
Notifications
You must be signed in to change notification settings - Fork 697
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
Add a 'status' command. #3643
Add a 'status' command. #3643
Conversation
sequenceA | ||
[ do strs <- HcPkg.check (hcPkgInfo conf) verbosity packagedb | ||
return (packagedb, strs) | ||
| packagedb <- packagedbs ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit surprised this works, since I thought ghc-pkg needs to know about all the package databases under you to check validity (otherwise some package references could look dangling.)
I think it would be far better for this program to quit if it can't read the LBI, rather than give possibly incorrect behavior. Better for a tool to give no info rather than bad info. I'm not sure why the compiler output is broken. (Too bad there's no tests ;) If I were SPJ, I'd check in some munged output of this to make sure that when we change the output it's acceptable. Need an 'accept' command though.) I'm very sorry that this (and the other PRs) died before we changed the branch access policy (you can see in the previous discussion @lspitzner asking if he can have write bits to maintainer this! Obviously he does now.) |
+1. Unreadable LBIs are a bottomless source of bugs and breakage. |
7c576a8
to
73e92bc
Compare
Rebased, addressed all of @ezyang's comments except #3643 (comment). |
73e92bc
to
d3ff4a9
Compare
2c9b1d3
to
2cdda02
Compare
Rebased. |
The 'status' command prints a summary over several aspects of a cabal environment, such as the Cabal and GHC versions, the package and its components, the package-databases, the sandbox etc.
4204dfc
to
57ea046
Compare
@23Skidoo: hi! what are your thought on the future of this command and PR? Would you like to work on that or perhaps comment on the design of a possible new version, drawing from many years of your experience with newer cabals? |
Feel free to close, I don't have the bandwidth to work on this at the moment. |
@23Skidoo |
thanks! |
#2882, rebased on top of
master
. Also moved the branch to the main repo so that others could push to it.Current status: needs more testing, there are apparently some bugs, e.g. #2882 (comment).