Just wondering whether it would make sense for MacPorts to auto exclude that folder? Does spotlight even provide an API or command that would allow MacPorts to do that?
André-John Sent from my phone. Envoyé depuis mon téléphone. > On 16 Nov 2021, at 21:03, Richard L. Hamilton <[email protected]> wrote: > > Good, thanks. Perhaps I wouldn't exclude the whole /opt/local (or whatever > install prefix) unless performance is a major issue, but > /opt/local/var/macports, which is less likely to be interesting in terms of > commands or configuration files or documentation, and both large (mine is > 24GiB when the entire /opt/local is only 35GiB - and I frequently remove most > inactive ports and run a port clean installed) and active in terms of changes. > >> On Nov 16, 2021, at 16:06, Chris Jones <[email protected]> wrote: >> >> >> I am not aware of any use macports itself makes of spotlight, so for sure if >> you don’t plan on using it yourself to search the install prefix, you can >> disable it. >> >>>> On 16 Nov 2021, at 6:26 am, Richard L. Hamilton <[email protected]> wrote: >>>> >>> Seems it'd thrash Spotlight a lot less during "port selfupdate" or "port >>> upgrade outdated" to exclude /opt/local, as long as that wouldn't break >>> anything (obviously one couldn't then use Spotlight to search /opt/local, >>> but that's ok with me). >>> >>> > > -- > eMail: mailto:[email protected] > > > >
