-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
brew cleanup
should continue even if it wasn't permitted to remove a file
#11924
Comments
This is generally considered a bug rather than a feature. We try to catch the relevant exceptions and continue but this is imperfect.
In this case, though, you should set |
No, don't get me wrong. I do want cleanup, I just want to hang on to certain files that have been linked to other executable.
I agree. Should I report it as bug instead? |
You can still pass a formula name to That said, I do think allowing |
No, I've relabelled it but consider this to be working as desired.
That's not cleanup, as far as we're concerned. |
I see. Is there a workaround, like registering packages to |
Not currently. This is what my suggestion above would do:
|
@andreasabel |
@MikeMcQuaid: Thanks! This might last me a while, until some apps demand a newer version of |
It turns out this wasn't too hard, and when you've got an itch... #11931 |
I've merged #11931. If you're on the |
@carlocab Wonderful, that's great! I tried |
Glad it's working for you. |
Provide a detailed description of the proposed feature
Current situation:
Atm,
brew cleanup
crashes instead of continuing to clean up.Feature suggestion: ignore errors, or at least if a flag like
--ignore-errors
,-i
is given.What is the motivation for the feature?
There might be dynlibs I want to hang on so that upgrades do not remove them. After all, other programs (outside of the
brew
universe) have been linked against than andbrew cleanup
breaks them mercilessly. A simple workaround is to forbidbrew
to remove this files by making them read-only, but thenbrew cleanup
crashes.How will the feature be relevant to at least 90% of Homebrew users?
I suppose only 10% use
brew
exclusively for everything.What alternatives to the feature have been considered?
N/A
The text was updated successfully, but these errors were encountered: