libyab.so

[lelldorin]

This is true, but yab has matured to the point that we are not re-working features and options, but rather adding new options to commands or new commands and not changing / removing old ones.

Who is we? yab is open source. every one can make changes if he like.

Even with all the changes made recently to textcontrol, there are no changes that broke older programs. With care, this will continue. If / when there is a break, libyab.so will be re-named to reflect this, and older programs will need to be re-compiled to use the new library. At that point, a libyab.so.hpkg may be required to allow older programs to continue to run.

Yes you do, but other people?

On the other hand, if we insist on having a libyab package so that our compiled programs can use this as a dependency instead of yab, this triggers the following.

Changing from two .hpkg files for yab to four.

Adding a libyab.hpkg

Adding a Libyab_devel.hpkg

Adding libyab.hpkg as a dependency for the yab .hpkg so that the yab.hpkg no-longer includes this lib.

Adding libyab-devel as a dependency to the yab_ide.hpkg as this will no-longer be included with the yab.hpkg that yab_ide.hpkg depends on.

The /system/lib folder will get a new libyab.so.xx file every time there is a change to yab as libyab is really where the yab code resides even though the library is backward compatible.

Compiled programs will need to refer to libyab.so.xx

I does ot can follow, i does not understand, my english is to bad and my google translation is to confusing