Skip to content
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

Closed
wants to merge 8 commits into from
Closed

Add a 'status' command. #3643

wants to merge 8 commits into from

Conversation

23Skidoo
Copy link
Member

@23Skidoo 23Skidoo commented Jul 29, 2016

#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).

sequenceA
[ do strs <- HcPkg.check (hcPkgInfo conf) verbosity packagedb
return (packagedb, strs)
| packagedb <- packagedbs ]
Copy link
Contributor

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.)

@ezyang
Copy link
Contributor

ezyang commented Jul 29, 2016

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.)

@23Skidoo
Copy link
Member Author

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.

+1. Unreadable LBIs are a bottomless source of bugs and breakage.

@23Skidoo 23Skidoo force-pushed the status-command branch 2 times, most recently from 7c576a8 to 73e92bc Compare August 15, 2016 00:17
@23Skidoo
Copy link
Member Author

Rebased, addressed all of @ezyang's comments except #3643 (comment).

@23Skidoo
Copy link
Member Author

Rebased.

Lennart Spitzner and others added 7 commits September 11, 2016 16:19
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.
@Mikolaj
Copy link
Member

Mikolaj commented May 22, 2021

@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?

@jneira
Copy link
Member

jneira commented Aug 18, 2021

this looks like the ide command @fendor is working on here #7500
the pov of @23Skidoo would be invaluable there but I would close this if the ide command is merged finally

@23Skidoo
Copy link
Member Author

Feel free to close, I don't have the bandwidth to work on this at the moment.

@jneira
Copy link
Member

jneira commented Aug 18, 2021

Feel free to close, I don't have the bandwidth to work on this at the moment.

@23Skidoo
sad to read that, btw many many thanks for the huge amount of hard work in all areas you have put in this project. Your mood has helped to make progress in many issues an prs.

@jneira jneira closed this Aug 18, 2021
@23Skidoo
Copy link
Member Author

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants