(09-01-2015, 10:30 PM)lelldorin Wrote: how do want to do that?

i am using yab sience first time. i often have to rebuild many of my programs to get all new features in yab for this in this time because the changes are to deep. so my apps does not run anymore because, for example changes on the window command (position of window be changed). this every month... this was hard and frustrating. if you use all the time the same package name the user can only install this and breaks eventually older programs. if we add at the library a Versionsnumber like all other libraries too we solve this problem. or we need one package, but must be inkluded all Versions. i think this point of libyab is not competly managed and we need to get a solution on this in order to does not break older programs.

what is the problem to compile with the version number included?
what kind of problem this have to you?

please do not forget that yab is open source and other ones (jan comes back on r1?) make his own version like you in the Future.

we need version specification

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.

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, 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 may be required to allow older programs to continue to run.

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 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

Messages In This Thread - by bbjimmy - 08-30-2015, 12:22 PM
RE: - by clasqm - 08-30-2015, 02:11 PM
RE: - by lelldorin - 08-31-2015, 02:27 PM
RE: - by bbjimmy - 08-31-2015, 03:19 PM
RE: - by lelldorin - 09-01-2015, 05:31 AM
RE: - by lorglas - 09-01-2015, 07:17 AM
RE: - by clasqm - 09-01-2015, 12:59 PM
RE: - by bbjimmy - 09-01-2015, 02:34 PM
RE: - by lorglas - 09-01-2015, 03:24 PM
RE: - by lelldorin - 09-01-2015, 03:43 PM
RE: - by bbjimmy - 09-01-2015, 04:23 PM
RE: - by lelldorin - 09-01-2015, 10:30 PM
RE: - by bbjimmy - 09-02-2015, 09:17 AM
RE: - by lelldorin - 09-02-2015, 11:31 AM
RE: - by clasqm - 09-02-2015, 03:12 PM
RE: - by lorglas - 09-02-2015, 10:37 PM
RE: - by clasqm - 09-03-2015, 05:10 AM
RE: - by lelldorin - 09-03-2015, 06:47 AM
RE: - by bbjimmy - 09-03-2015, 10:50 AM
RE: - by lelldorin - 09-03-2015, 11:25 PM
RE: - by bbjimmy - 09-04-2015, 08:54 AM
RE: - by clasqm - 07-25-2016, 01:29 AM
RE: - by bbjimmy - 07-25-2016, 02:40 PM

Forum Jump:

Users browsing this thread: 1 Guest(s)
Free Web Hosting