[Gambas-bugtracker] Bug #2901: Packages dependies (step 7 of packager)

[<bugtracker@xxxxxxxxxxxxxx>]

http://gambaswiki.org/bugtracker/edit?object=BUG.2901&from=L21haW4-

Comment #38 by Brian G:

I have addressed these issues and have added for complex usage.

use "library:0" ' which does seem to correctly use the latest by default
And the main version only changes when the interface/compatibility changes.

I add a startup module to my apps and manage the versions myself. I use a text file from the project to contain the info.
It seems things are getting supper complicated here.

I just prompt the user to install or offer to install the correct version when not present.
For specific customers, I have a private ppa that can be checked as well by the app.

The other method I use for fixed dependency is to push the library into the install set
generated for the app.

I don't know this whole naming max min etc, has been long solved by simple using version numbers in a way that
delineates the apps usage profile. eg 1.x.x is the library/interface level, 1.1.x means the interface changed/extended but is still compatible and 1.1.1 means there are updates and changes.

your app can check which are available.

for such a complicated requirement should not the app be doing some of the work.

Just a thought from my experience, maybe I really don't understand the worry here.



----[ Gambas bugtracker-list is hosted by https://www.hostsharing.net ]----