Opened 3 months ago
Last modified 3 months ago
#70633 new enhancement
Add an option for `port reclaim` to clean up old log files
Reported by: | cooljeanius (Eric Gallager) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.10.0 |
Keywords: | Cc: | ||
Port: |
Description
On my system, /opt/local/var/macports/logs
currently takes up 61.4MB of space. Some of the logs in there don't get cleaned up by sudo port -udc clean --all all
. Would it be possible to have port reclaim
handle this?
Change History (4)
comment:1 Changed 3 months ago by cooljeanius (Eric Gallager)
comment:2 Changed 3 months ago by jmroot (Joshua Root)
Type: | defect → enhancement |
---|
comment:3 follow-up: 4 Changed 3 months ago by ryandesign (Ryan Carsten Schmidt)
sudo port clean all
should remove logfiles for all known ports. Unknown ports (for example ports that have been deleted) are unknown to MacPorts so it can't do anything about them.
I was not aware that the registry would ever contain anything that was unused. What's an example of that?
comment:4 Changed 3 months ago by cooljeanius (Eric Gallager)
Replying to ryandesign:
sudo port clean all
should remove logfiles for all known ports. Unknown ports (for example ports that have been deleted) are unknown to MacPorts so it can't do anything about them.
I mean, it can still see that the files are there, though, so can't it just clean them up anyways, without having to know their ports?
I was not aware that the registry would ever contain anything that was unused. What's an example of that?
I'm just looking at directories under /opt/local/var/macports/registry/portfiles
, and it's got stuff like ports from old perl versions that no longer exist like perl5.24 in there; is there any reason to keep things like that?
Kinda related: I wonder if it'd be possible to purge old unused entries from the registry, too? Some of the stuff under
/opt/local/var/macports/registry
is also taking up a lot of room...