OK, today's package build, on the small (work) package set, something is dragging in not only chromium but an enormous pile of python crap and rust-nightly and node and Ghu only knows what else I'm about to learn about.
Can anyone suggest an efficient way to determine which port is dragging in this shit? Google is not being helpful. @_bapt_?
By deliberately breaking the chromium Makefile I found that the following ports have a mysterious, irrelevant dependency on chromium:
postgresql16-server-16.15
py312-redis-8.1.0
git-2.55.0
py312-pip-23.3.2_4
subversion-1.14.5_1
bind-tools-9.20.29
bind920-9.20.29
emacs-nox-31.1_2,3
curl-8.22.0
graphviz-16.1.0
p5-GD-Graph-1.56
p5-GD-TextUtil-0.86_5
nfs-exporter-0.4.7_2
nrpe-4.1.3
super_mediator-1.6.0_3
yaf-2.13.0_1
py312-cloud-init-25.2_1
cleanfeed-20200402_1
p5-News-Article-1.27_4
gnupg-2.5.21
nmap-7.991
openssh-portable-10.5.p1_1,1
pam_yubico-2.27_1
py312-certbot-4.2.0,2
silktools-3.22.2
fish-4.9.1_1
py312-ansible-14.4.0
ipmi_exporter-1.10.1_17
jail_exporter-0.18.0_9
openvox-server8-8.14.1
password-store-1.7.4_7
apache24-2.4.68_1
ap24-mod_auth_openidc-2.4.20.3
...what do all these ports have in common that they've grown a nonsense dependency on www/chromium?
I should note that this happened after a git update to 0a148187af543fa93a50948fbbb7de6c016313d0 this afternoon (plus our local changes, none of which involve chromium, this is a server build). Previous build was a week ago exactly and didn't have any of this.