-
Notifications
You must be signed in to change notification settings - Fork 67
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
Make fink cleanup --all
clean harder (or add a fink cleanup --everything
option?)
#220
Comments
...to give some more specific numbers, the disk space that this would save for me on my current system is approximately 20.56GB. |
I set my build dir to /tmp/ so it all vanishes on reboot :-) I also tend to keep my tarballs because there have been a few cases where the old ones vanish, but that's just me. My /opt/sw/src is 7.4gb right now, nothing for a 2tb nvme :-) (so glad there are adapters to let you use normal nvme with the older intel machines) |
The idea for the fink-implemented features was things that couldn't be done easily by hand, such as operating on the the internal dpkg database or using fink package data. If you want to just nuke /opt/sw/src even in-use tarballs and abandoned builddirs, that's just 'rm -rf'. I put my builddir in /opt/sw/build.build so I can control it separately from tarballs. But I can see a use-case for someone who doesn't know about all these fancy pathnames or cool things one can accomplish by changing them. For actions that could affect packages still "live" in the databases, probably best to use buildlock to avoid interfering with any packages that actually are in the process of being built. |
Yeah I always feel a bit hesitant about |
I would like an option to make fink clean up even more things than
fink cleanup --all
currently does: specifically, unfinished builds, and all source tarballs. This would help save me a lot of disk space.The text was updated successfully, but these errors were encountered: