-
Notifications
You must be signed in to change notification settings - Fork 676
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
Feature request: granular v2-clean #7857
Comments
Seems reasonable enough. My one question/concern would be the proper behavior if one is cleaning something lower in the build tree -- I'd think that "clean" would have to calculate that it needs to also clean the things dependent on it -- i.e. if one has a library, with a dependent executable, cleaning the lib would necessarily also mean cleaning the exe. |
This could be aligned with some discussion around #7851 about implementing |
This overlaps directly with the work I'm doing right now on scripts as is affects both how targets are calculated and the clean command. |
Dupe? #7506 |
What's the procedure for duplicate tickets? Should this be closed in favour of the pre-existing one? |
Duplicate of #7506 |
@TeofilC: if you are satisfied the other ticket covers your needs, please do close this one and keep the discussion/work alive on the other one. Thank you for your feedback! |
Sounds good to me! |
Motivation
As far as I know cabal currently only supports wiping out all build artefacts.
Yet, I'm often in a situation where I only want to do this to a package or component.
This can be worked around by doing something like
rm -r dist-newstyle/$PACKAGE
, but it would be nice ifcabal-install
supported this directly.Proposal
cabal clean
when not given any further arguments stays as it is.cabal clean [targets]
wipes out only the build artefacts fortargets
.If this sounds reasonable I'd be happy to give implementing it a go.
The text was updated successfully, but these errors were encountered: