Lazarus 3.4 Win x64, zstream does not have TGZip(De)compressionStream declared

[kzappa]

Hello good people of lazarus-land!
i just fresh install Lazarus 3.4 for windows x64 and i found that zstream unit that comes along with Lazarus 3.4 installation didnt have TGZipcompressionStream and TGZipDecompressionStream declaration. I was looking at zstream.pp source code in the paszlib package from official fpc gitlab repo and found difference comparing to the zstream.pp in Lazarus 3.4 installation. The declaration of TGZipcompressionStream can be found at line 516 in this zstream.pp file:  https://gitlab.com/freepascal.org/fpc/source/-/blame/main/packages/paszlib/src/zstream.pp#L516

The zstream.pp from Lazarus 3.4 installation however didnt even reach 500 line. I noticed a contribution made by user Van Canneyt about 2 years ago by adding gzstream routines (https://gitlab.com/freepascal.org/fpc/source/-/commit/3827889e61939ab1fa387cf5679bf239fd0715fe thank you so much Van Canneyt!). but i guess this patch didnt make it into Lazarus 3.4 installation

[dsiders]

Hello good people of lazarus-land!
i just fresh install Lazarus 3.4 for windows x64 and i found that zstream unit that comes along with Lazarus 3.4 installation didnt have TGZipcompressionStream and TGZipDecompressionStream declaration. I was looking at zstream.pp source code in the paszlib package from official fpc gitlab repo and found difference comparing to the zstream.pp in Lazarus 3.4 installation. The declaration of TGZipcompressionStream can be found at line 516 in this zstream.pp file:  https://gitlab.com/freepascal.org/fpc/source/-/blame/main/packages/paszlib/src/zstream.pp#L516

The zstream.pp from Lazarus 3.4 installation however didnt even reach 500 line. I noticed a contribution made by user Van Canneyt about 2 years ago by adding gzstream routines (https://gitlab.com/freepascal.org/fpc/source/-/commit/3827889e61939ab1fa387cf5679bf239fd0715fe thank you so much Van Canneyt!). but i guess this patch didnt make it into Lazarus 3.4 installation

Lazarus releases ship with the latest stable FPC compiler - which is FPC 3.2.2 for Lazarus 3.4. The commit you quote has not been included in an FPC release, because there hasn't been an FPC release since the change was made.

You can always download and install the FPC trunk compiler if you really need it.

[kzappa]

thankyou for the explanation sir. i think ill just have to wait for the changes made into the next release   

[Thaddy]

If it was 2 years ago, MvC committed that, there is a chance it is in fixes, so first examine the fixes branch: then it will be in the next release which is right now officially frozen, awaiting release and this is not a bug-fix but a feature. So it might stay in trunk for the time being.

[JuhaManninen]

You can also copy the gzstream sources from FPC trunk to your project. Very likely they compile with the current release FPC, too.

[paweld]

This change is in the 3.2-fixes branch, so as @Thaddy wrote, it will be in the upcoming release: 3.2.4

[JuhaManninen]

This change is in the 3.2-fixes branch, so as @Thaddy wrote, it will be in the upcoming release: 3.2.4

That is surprising. Adding a library is a new feature, not a bug fix. The FPC project mixes the concepts of a bug fix dot-release and a major release.
It is OK to have many years between major releases but bug fix releases should come often and should contain only pure bug fixes.
This mess-up may explain why the dot-release is taking so long (over 3 years).
Not good...

[440bx]

It is OK to have many years between major releases but bug fix releases should come often and should contain only pure bug fixes.
This mess-up may explain why the dot-release is taking so long (over 3 years).
Not good...

I just wanted to voice my agreement with the above.

I don't understand the reason to hold bug fixes in a non-official release.

I'd support something like having a bug fix release every six months or so.  At least that would show the project is alive and ever progressing.