-
Notifications
You must be signed in to change notification settings - Fork 698
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
Per package/component cabal clean
(add support for targets)
#7506
Comments
I guess we'd need to delete the package or component files and the common files. The trouble is identifying those, in particular if they are not generated with What does |
I see there is option
I wonder what's 'configuration' and 'artifacts' and if there is anything more. Code-diving would help. |
As far as I can tell, that flag is just being ignored, but the code path should delete only |
OK, so we discovered a bug as well. |
Looks rather intentional to me:
|
May it be that 'configuration' is only However, if 'configuration' is |
I think currently However, the help message from
Not exactly the same flag but looks similar. Maybe Regarding the issue, I think there are two ways of tackling this:
|
As I mentioned on #7857, I'd be interested in trying to implement this. On the other ticket:
|
cabal clean
cabal clean
(add support for targets)
|
cabal clean
is both simple and effective, by virtue of just deleting everything. However, in a multi-package project, I usually want to clean just one package or component that I'm working on.Of course, the current implementation works for this, but once you accrue a few local packages and a few
source-repository-package
s, redoing all the work instead of just the last bit becomes painful.At the moment I work around this by deleting targeted fragments of
dist-newstyle/build
. This works, but:I think it would be nice to provide a per package/component
cabal clean
, and hopefully it would just be a matter of listing all the relevant files and deleting them.The text was updated successfully, but these errors were encountered: