Skip to content
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

Open
cooljeanius opened this issue Jan 24, 2021 · 5 comments

Comments

@cooljeanius
Copy link
Contributor

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.

@dmacks
Copy link
Member

dmacks commented Jan 24, 2021

@cooljeanius
Copy link
Contributor Author

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.

...to give some more specific numbers, the disk space that this would save for me on my current system is approximately 20.56GB.

@beren12
Copy link
Member

beren12 commented Sep 24, 2023

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)

@dmacks
Copy link
Member

dmacks commented Sep 25, 2023

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.

@cooljeanius
Copy link
Contributor Author

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'.

Yeah I always feel a bit hesitant about rm -rf-ing anything; having it supported as a built-in fink command would help give me a bit more peace of mind that I'm actually allowed to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants