[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gambas-bugtracker] Bug #2901: Packages dependies (step 7 of packager)
[Thread Prev] | [Thread Next]
- Subject: [Gambas-bugtracker] Bug #2901: Packages dependies (step 7 of packager)
- From: <bugtracker@xxxxxxxxxxxxxx>
- Date: Fri, 22 Nov 2024 13:00:43 GMT
- To: gbWilly@xxxxxxxxxxxxxx,bugtracker@xxxxxxxxxxxxxxxxxxxxxx
http://gambaswiki.org/bugtracker/edit?object=BUG.2901&from=L21haW4- Comment #9 by Willy RAETS: I've been working as you said for a while now, but now I run into trouble. Below are the properties of my library (LibGb3Base), set to be compatible until 1.0.0 Next you see how the depended application (MyManger) has been installed depending on gb-libgb3base (min version 0.1.21 and no max version -> is in library above) Yesterday I released and installed new version of LibGb3Base being 0.2.0 and installed it. (see image of Synaptic to see what is installed) Today I opened MyManger, but it wouldn't start, so I started it from terminal with debug argument to see what is wrong. It turned out that it wouldn't start because of missing library, although installed! Switching library version from 0.1.21 to 0.1.22 works, but going from 0.1.21 to 0.2.0 seems to be problematic, although library is set to be compatible until 1.0.0 My version system is as follows" 0.0.1 and up -> new application in development, only used by me during development 0.1.0 and up -> now we are in Alpha branch, so few people will work with it (dedicated testers) 0.2.0 and up -> now we are in Beta branch, aimed at no more new features and bugfixing etc (some minor needed additions are allowed), wider testing 0.3.0 and up -> now we are at Release Candidates, no more additions, all start using, only bugfixes 1.0.0 and up -> first stable release 1.1.0 and up -> first release with new additions compared to 1.0.0 branch etc. So, switching one of my Libraries to 0.2.0 (from Alpha to Beta) broke all installed applications depending on an Alpha version number of that library. I can solve by repacking with 0.2.0 as dependency, that works, but it is not the behavior I would expect, after our earlier discussion on this topic. ---------------------------------------------------------------------------- Attachment: Dependencies-CompatibleUntil.png Attachment: Dependencies-step7.png Attachment: Dependencies-Installed.png Attachment: Dependencies-Problem.png ----[ Gambas bugtracker-list is hosted by https://www.hostsharing.net ]----