First, I don't see why you need the rich deps here. Wouldn't a
`libfoo.so.1(do_foo@FOO_1.0)(64bit))` requires be enough?
Then, wouldn't your proposal mean that over time you'll have a provide for
every symbol? That'll be quite some burden on the metadata size and dependency
solver setup. If
My understanding is that set-versions imposes the same requirement, only that
it's inscrutable to the user because it's hashed rather than in
user-comprehensible form.
You're correct that it may not necessarily require rich deps, though. I was
thinking of cases where a library may provide
