-
Notifications
You must be signed in to change notification settings - Fork 4
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
stack-clean-old purge-older
may say nothing
#6
Comments
Thanks for this, Andreas: that does sound like a nice approach. |
I now realize |
I have implemented |
- bump version to 0.4 - replace Bool with Deletion type
I pushed my changes - if you want to test it before I make a release that would be helpful too. |
I tried your |
(Also 0.4 was finally released.) I will leave this open for now so I can try to revisit it at some point. |
I played around with 0.4 a bit. It is nice that
The OP is still open, but you already stated that this is future work. |
Ah that is a good point! I will probably add an link to the readme too. |
Okay I released 0.4.1 to hackage with that. |
stack-clean-old purge-older --dry-run
may say nothingstack-clean-old purge-older
may say nothing
I am getting
Would be nice if I was told explicitly that there is nothing to purge, or a list of what would be purged.
Btw, I wrote something similar (but less feature-rich) for cabal, see https://github.com/andreasabel/cabal-clean.
I made
--dry-run
is the default. If you call it without arguments, you get a list of all build artefacts that are there, in green color those that will be kept, in red color those that would be deleted. To remove stuff, you have to supply option--remove
/--delete
.Maybe such an interface would also work for
stack-clean-old
.The text was updated successfully, but these errors were encountered: