Actually, I wanted to check whether executables in texlive-bin rely on dvisvgm.

Answer: /usr/bin/cluttex can use dvisvgm.

Therefore, texlive-bin should optdepend on dvisvgm.

Anyway, while grep-ing the executables for mentions of dvisvgm, I found that
texlive-bin 2023.66984-7 comes with lots of dangling symlinks:

```
$ pacman -Qlq texlive-bin | grep /bin/. | LANG=C xargs ls -H >/dev/null
ls: cannot access '/usr/bin/cjk-gs-integrate': No such file or directory
ls: cannot access '/usr/bin/convbkmk': No such file or directory
ls: cannot access '/usr/bin/ebong': No such file or directory
ls: cannot access '/usr/bin/jamo-normalize': No such file or directory
ls: cannot access '/usr/bin/jfmutil': No such file or directory
ls: cannot access '/usr/bin/kanji-config-updmap': No such file or directory
ls: cannot access '/usr/bin/kanji-config-updmap-sys': No such file or directory
ls: cannot access '/usr/bin/kanji-config-updmap-user': No such file or directory
ls: cannot access '/usr/bin/kanji-fontmap-creator': No such file or directory
ls: cannot access '/usr/bin/komkindex': No such file or directory
ls: cannot access '/usr/bin/mkgrkindex': No such file or directory
ls: cannot access '/usr/bin/ptex2pdf': No such file or directory
ls: cannot access '/usr/bin/rubibtex': No such file or directory
ls: cannot access '/usr/bin/rumakeindex': No such file or directory
ls: cannot access '/usr/bin/ttf2kotexfont': No such file or directory
```

This is not a case of simple misdirection.
Nothing with the same basename exists anywhere in texlive-bin.
To see this, run:

```
dangling=$(pacman -Qlq texlive-bin | grep /bin/. | while read exe; do [ -e "$exe" ] || echo "${exe##*/}"; done)
pacman -Qlq texlive-bin | grep -F "$dangling"
```

Those links should be removed, or the intended targets should be found and included in the package.