SSR: depend on version 10 of the fmt library

[mgeier]

This tries to pin the version of libfmt, but I'm not sure if that's the right syntax (nor if that works at all).

See #32.

[mgeier]

I'm not sure whether the CI failure has anything to do with my change ...

[mgeier]

I guess not: https://github.com/orgs/Homebrew/discussions/5441

[HaHeho]

To explain this here. The SSR doesn't actually depend on v10, but the bottle links against it since it was the latest version on creation.

The preferred solution would be that the SSR build links a generic libfmt.dylib instead of specifically either libfmt.10.dylib or libfmt.20.dylib.

[mgeier]

The preferred solution would be that the SSR build links a generic libfmt.dylib instead of specifically either libfmt.10.dylib or libfmt.20.dylib.

That's not possible, though, because "a generic libfmt.dylib" doesn't exist. libfmt.10.dylib and libfmt.20.dylib are ABI incompatible, as shown by the different major versions.

If we cannot depend on a specific version of fmt (and I tried multiple ways in this PR, none seems to work), I think the only alternative is to create new bottles which depend on version 11: #35.

[HaHeho]

That's not possible, though, because "a generic libfmt.dylib" doesn't exist. libfmt.10.dylib and libfmt.20.dylib are ABI incompatible, as shown by the different major versions.

Thanks for explaining.

If we cannot depend on a specific version of fmt (and I tried multiple ways in this PR, none seems to work), I think the only alternative is to create new bottles which depend on version 11: #35.

Yes, I think this is a decent (and maybe only) solution. After that, if someone executes a generic brew upgrade, then fmt and ssr would both be upgraded and ABI compatible.
I'm not sure what happens if libfmt.10.dylib (outdated) is already installed while an upgraded SSR (#35) is installed for the first time. But even if that could create a problem, it is quite unlikely to occur.

[mgeier]

I'm not sure what happens if libfmt.10.dylib (outdated) is already installed while an upgraded SSR (#35) is installed for the first time.

I cannot try this because the only Mac I have access to has macOS 12 installed.
But even it that scenario doesn't work, I gues a brew upgrade should fix it, as you said.

In any case, if there are problems with libfmt, a re-installation of ssr with --build-from-source should be a reasonable work-around.