In that case I am splitting out all the shared libraries into one libcflsh0 (and it's libcflsh-dev counterpart) package to make sure we have an easy way to handle ABI breakages and transitions. Normally we'd split out each library into its own package but after inspecting the source I saw that all of the generated libraries are handled by a single SOVER, so during an ABI break it would just bump the soname for all libraries anyway. After some additional minor cleanup and sanity testing I would expect it to be good to go for review.
In that case I am splitting out all the shared libraries into one libcflsh0 (and it's libcflsh-dev counterpart) package to make sure we have an easy way to handle ABI breakages and transitions. Normally we'd split out each library into its own package but after inspecting the source I saw that all of the generated libraries are handled by a single SOVER, so during an ABI break it would just bump the soname for all libraries anyway. After some additional minor cleanup and sanity testing I would expect it to be good to go for review.