Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2024-06

Multiple versions of the same package and its dependencies?

5 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Luca Olivetti

Hello,

I have a problem with one project and zeosdbo, so I'm trying different versions of zeosdbo.
In the project inspector I change the min/max version of the required package (zcomponent) so it uses the one I want to try. Lazarus knows all versions of the zcomponent package so it doesn't flag the requirement as missing, however zcomponent itself depends on other packages of the same version and lazarus marks them as missing until I open the lpk one by one.
This happens every time I try to change the version of the required zcomponent.
Shouldn't lazarus already know the different versions of all the packages? This is with lazarus 3.2 btw, I didn't yet try 3.4

Bye

Luca Olivetti Wetron Automation Technology https://wetron.es/ Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007

Reply by email

Michael Van Canneyt
to Luca Olivetti
Luca Olivetti wrote 14 lines
Hello, I have a problem with one project and zeosdbo, so I'm trying different versions of zeosdbo. In the project inspector I change the min/max version of the required package (zcomponent) so it uses the one I want to try. Lazarus knows all versions of the zcomponent package so it doesn't flag the requirement as missing, however zcomponent itself depends on other packages of the same version and lazarus marks them as missing until I open the lpk one by one. This happens every time I try to change the version of the required zcomponent. Shouldn't lazarus already know the different versions of all the packages? This is with lazarus 3.2 btw, I didn't yet try 3.4

The zeos packages themselves need to indicate the min/max versions of the packages they depend on. Then, if lazarus needs to decide the dependencies, it will select the correct ones if it knows them.

I used the versioning extensively, and it works fine, but every package must "play nice" before it can work correctly.

Michael.

Reply by email

Werner Pamler
to Luca Olivetti: I have a problem with one project and zeosdbo, so I'm trying different versions of…
Luca Olivetti wrote 13 lines
I have a problem with one project and zeosdbo, so I'm trying different versions of zeosdbo. In the project inspector I change the min/max version of the required package (zcomponent) so it uses the one I want to try. Lazarus knows all versions of the zcomponent package so it doesn't flag the requirement as missing, however zcomponent itself depends on other packages of the same version and lazarus marks them as missing until I open the lpk one by one. This happens every time I try to change the version of the required zcomponent. Shouldn't lazarus already know the different versions of all the packages? This is with lazarus 3.2 btw, I didn't yet try 3.4

Hard disk space is cheap. Make a second ("secondary") installation of Lazarus?in which you can install the other version of zeos.

Reply by email

Luca Olivetti
to Michael Van Canneyt: The zeos packages themselves need to indicate the min/max versions of the packages they…

El 4/6/24 a les 15:17, Michael Van Canneyt via lazarus ha escrit:

Show quoted text 7 lines
> Shouldn't lazarus already know the different versions of all the > packages? > This is with lazarus 3.2 btw, I didn't yet try 3.4 The zeos packages themselves need to indicate the min/max versions of the packages they depend on. Then, if lazarus needs to decide the dependencies, it will select the correct ones if it knows them.

Yes, they do, they specify a min/max corresponding to the version, i.e.:

zcomponent 7.1.4 requires
zplain >=7.1 <=7.1
zparsesql >=7.1 <=7.1
zdbc >=7.1 <=7.1
zcore >=7.1 <=7.1

zplain requires
zcore >=7.1 <=7.1

zparsesql requires
zcore >=7.1 <=7.1

zdbc requires
zplain >=7.1 <=7.1
zparsesql >=7.1 <=7.1
zcore >=7.1 <=7.1

but I have to open the lpk of all the packages every time I want to switch from 7.1.4 to 7.2.12 and viceversa otherwise lazarus complains about missing packages.

I used the versioning extensively, and it works fine, but every package must "play nice" before it can work correctly.

Maybe the problem is because the packages only specify major/minor instead of major/minor/revision?

Another question is, my projects using zeos automatically acquired the version I used when I wrote them (e.g. zcomponent >=6.5), since both 7.1 and 7.2 (and 8.0) satisfy the requirement, which version will the project actually use? The last one I opened the lpk, the one installed in the ide or the higher version available?

Bye

Luca Olivetti Wetron Automation Technology https://wetron.es/ Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007

Reply by email

Luca Olivetti
to Werner Pamler: Hard disk space is cheap. Make a second ("secondary") installation of Lazarus?in which…

El 4/6/24 a les 15:52, Werner Pamler via lazarus ha escrit:

> This is with lazarus 3.2 btw, I didn't yet try 3.4 Hard disk space is cheap. Make a second ("secondary") installation of Lazarus?in which you can install the other version of zeos.

That's an option, yes, in fact I already keep several versions of lazarus

du -sh laz_*
2,9G laz_1_6
3,0G laz_1_8
5,8G laz_2_0
4,6G laz_2_2
4,0G laz_3_2

(I also have 1_4 in a different directory plus some more special versions in virtual machines).

I just wanted to know if I can specify an hard requirement on a specific version of a package and have lazarus automatically resolve it.

Bye

Luca Olivetti Wetron Automation Technology https://wetron.es/ Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007

Reply by email