Add libe57format/3.2.0 release

[EstebanDugueperoux2]

Summary

Changes to recipe: libe57format/3.2.0

Motivation

Add 3.2.0 release

[jcar87]

Thanks @EstebanDugueperoux2 - please only make the changes required by the PR objetive (adding 3.2.0) - we've had issues with hasty removals of old logic leading to unintended bugs. For the time being, the team will try to take on these clean ups after the PR has been reviewed and if it doesn't cause delays in merging a useful feature.

[EstebanDugueperoux2]

Thanks @EstebanDugueperoux2 - please only make the changes required by the PR objetive (adding 3.2.0) - we've had issues with hasty removals of old logic leading to unintended bugs. For the time being, the team will try to take on these clean ups after the PR has been reviewed and if it doesn't cause delays in merging a useful feature.

Hi @jcar87, the issue is that only adding new release make pipeline failed.
And it seems patch done inside the recipe is no more usefull.

[jcar87]

Hi @jcar87, the issue is that only adding new release make pipeline failed.

mmm, we can have a look, what was the CI failure in this case?

And it seems patch done inside the recipe is no more usefull.

The removal of the _patch_sources() method is in effect for all already published versions, so it is introducing regressions for pre-existing versions w.rt. POSITION_INDEPENDENT_CODE, and introducing a regression for 3.1.1 by removing the warnings as errors - if this PR were merged, it could cause issues to users of 3.1.1 -

And it seems patch done inside the recipe is no more usefull.

We keep asking contributors to avoid these kind of changes because we very often see that they are more invasive and have side effects that are not intended, as it seems to be the case here

[EstebanDugueperoux2]

Hi @jcar87 I have updated recipe to relax replace_in_file with strict=False because "set_warning_as_error()" doesn't exists anymore in recent release.
It was the cause of previous pipeline failures.

[jcar87]

Thanks for amending the PR!