alsa-lib: update to 1.2.3.2.

[ailiop-git]

No description provided.

[ahesford]

You have other PRs, like an mpg123 update, that link against alsa-lib-devel. While it might not matter for shlib compatibility, in the future, please combine things like alsa-lib and dependants like mpg123 in a single PR with commits ordered to ensure that the new alsa-lib is built before anything that builds against it.

[ailiop-git]

You have other PRs, like an mpg123 update, that link against alsa-lib-devel. While it might not matter for shlib compatibility, in the future, please combine things like alsa-lib and dependants like mpg123 in a single PR with commits ordered to ensure that the new alsa-lib is built before anything that builds against it.

Since there's no shlib compatibility issue, why should those updates be combined?

[ahesford]

The shlib dependency resolution in XBPS and xbps-src helps prevent a lot of problems, but that doesn't mean subtle issues can't appear when one updates a library and its headers but doesn't rebuild against the new version. Even if there are no problems, it's possible that the build objects can differ in some meaningful way when built against an older version of the library, which means versions built by xbps-src after the library is updated will be different than the official binary packages for no apparent reason.

Obviously we accept this tradeoff every time we update a library because revbumping every dependant of every library "just in case" isn't worth the cost. But if you're updating a dependent and a library within a few hours of one another, why not ensure proper ordering just to ensure consistency?