[MacPorts] #70556: "base" seemingly locking up for sometimes very long
MacPorts
noreply at macports.org
Sun Sep 8 12:52:34 UTC 2024
#70556: "base" seemingly locking up for sometimes very long
--------------------------+--------------------
Reporter: RJVB | Owner: (none)
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: base | Version:
Resolution: | Keywords:
Port: |
--------------------------+--------------------
Comment (by barracuda156):
Replying to [comment:16 RJVB]:
> Do you have sqlitebrowser installed, or do you know how else to
determine what your registry's pagesize is set to?
(https://www.sqlite.org/pragma.html#pragma_page_size)
I can try to check that.
BTW, once I tolerated that procedure once without killing it, it is back
to normal now, like it was with 2.9.x (or at least it seems so, no more
ridiculous freezing).
> That, plus what's the architecture of the machine you're on and how
fragmented is the drive holding the registry (if it's a spinning disk)?
It is an SSD, but with no too much space left (at the time of original
post perhaps some 10 GB). I did some cleaning ever since, so that ccache
and other stuff can use more disk space when needed.
> Transparent FS compression doesn't exist on Mac unless you install ZFS
(www.o3x.org) but while it has become stable and fast I wouldn't advise it
unless you keep very regular backups.
I am not sure it is even supported in any build of 10.6 (a few of them has
some ZFS-related components, not sure if FAT or x86-only) and won’t risk
using it in any case.
> I think you should evaluate how much old luggage there is in your
installation, and uninstall anything you really don't need anymore. If you
make a backup of $prefix/var/macports/registry and the corresponding files
under $prefix/var/macports/software you can always reinstall ports you
shouldn't have uninstalled, with a bit of manual hackery.
> But, this cleanup will probably be a lengthy process: I have no idea how
good MacPorts is in automatically uninstalling only the appropriate
versions of dependencies and/or dependents of a given port version, while
leaving all the other versions.
> Not very good I'm afraid, if it is any indication that `port dependents
foo` will list every port you have installed that once depended on
`port:foo`.
Somewhat on a side note, if there a way to deactivate all ports and then
activate back specifically those which were active prior to that? Some
port conflict with each other, so `activate installed` will not work, and
sorting that by hand gonna be annoying.
A simple use case: I want to make a clean build of something, being sure
that no irrelevant stuff gets linked in (build-bot-style build). But then
I want my ports active back, because otherwise I do not know what gets
updated.
--
Ticket URL: <https://trac.macports.org/ticket/70556#comment:17>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list