There is need for only one libyab.so on the system. libyab.so IS backward compatible.
If one has a program compiled with yab1.7.5 and later installs yab 1.7.6, the program made with 1.7.5 will still run properly even though libyab,so was replaced and updated with the later yab version.
The problem with a libyab hpkg is that currently there is no versioning of libyab.so, and simply requiring libyab.so may break things. Requiring yab >= 1.xx solves the breakage. If I make a libyab .hpkg, it will have versioning that matches the yab version making it necessary to specify the libyab version, libyab.so >= 1.xx, just like one now needs to do with yab.
Again, lots of work for little benefit.
If one has a program compiled with yab1.7.5 and later installs yab 1.7.6, the program made with 1.7.5 will still run properly even though libyab,so was replaced and updated with the later yab version.
The problem with a libyab hpkg is that currently there is no versioning of libyab.so, and simply requiring libyab.so may break things. Requiring yab >= 1.xx solves the breakage. If I make a libyab .hpkg, it will have versioning that matches the yab version making it necessary to specify the libyab version, libyab.so >= 1.xx, just like one now needs to do with yab.
Again, lots of work for little benefit.
