08-30-2015, 12:22 PM
I have recently noticed an .hpkg file offered by BeSly.de ... http://www.software.besly.de/ for libyab.so.
This may be the way we want to go, however this will require us to version the lib. As it works now, one would package his yab program with the libyab.so that was used to make it, or specify the minimum yab version used as a package requirement. If we break out the library into its own package, we must require a minimum version of the lib ( just as we required a minimum version of yab ) to insure that we are using a version that works with the program.
If we do this, we get into the whole libyab,.so.1 ... libyab.so.1.1 etc mess. It can be done this way, but I think requiring the proper yab version or simply adding a lib folder with libyab.so is simpler.
What are your thoughts?
This may be the way we want to go, however this will require us to version the lib. As it works now, one would package his yab program with the libyab.so that was used to make it, or specify the minimum yab version used as a package requirement. If we break out the library into its own package, we must require a minimum version of the lib ( just as we required a minimum version of yab ) to insure that we are using a version that works with the program.
If we do this, we get into the whole libyab,.so.1 ... libyab.so.1.1 etc mess. It can be done this way, but I think requiring the proper yab version or simply adding a lib folder with libyab.so is simpler.
What are your thoughts?
