Arch Linux prebuilt release depends on outdated libyaml-cpp.so

[PerfectlyInternal]

When using the prebuilt binary for Arch Linux, it crashes due to missing libyaml-cpp.so.0.8. The latest version of libyaml on Arch is 0.9, so this would require a downgrade. A temporary workaround I've found is to symlink libyaml-cpp.so.0.8 to libyaml-cpp.so.0.9, which seems to work without issue.

This seems to be caused by an update to libyaml-cpp since the release. If possible, it would be nice to have the prebuilt binaries use whatever version is available on the system, instead of specifying a particular number.

[azonenberg]

I don't think there's any way to link to an arbitrary soname, the version number probably changed because of some ABI-breaking change between 0.8 and 0.9 that you happened to not hit.

Release binaries will be built for whatever library versions are current at the time of the release and I'm not sure there is any good alternative to this.

Version 0.2 will be coming out later this month and should depend on libyaml-cpp 0.9. You can grab a prebuilt binary from the CI server if you want to play with the latest development version in the meantime. As of this writing that would be https://dl1.ngscopeclient.org/ngscopeclient-ci/2026/06/2026-06-07-1340PDT-904b973e/arch-amd64/ngscopeclient-0.1.1-578-g904b973e-Linux.tar.gz.