Ideas of upgrades and additions to mfext and addon scientific

[thebaptiste]

• upgrade geos >= 3.9.0 (mfext)
• upgrade gdal >= 3.3.1 (mfext)
• upgrade proj >= 8.1.0 (mfext)
• upgrade json-c >= 0.15 (mfext) ==> We use system json-c now
• upgrade from python 3.8 to python 3.9 (mfext)
• move protobuf >= 1.4.0 to mfext from addon scientific ? This format is more and more used, postgis doesn't build by default without it (option --without-protobuf required) : https://developers.google.com/protocol-buffers
• add librttopo in mfext ? (for lwgeom includes, not provided anymore by postgis, which is indicated as a "minor breaking change" in postgis changelog) : https://git.osgeo.org/gitea/rttopo/librttopo
• add zeromq/libzmq (mfext) ? zeromq-devel required to build pyzmq in layer python3_circus with python3.9 but releases are very different in CentOS6 and CentOS8 : [https://github.com/zeromq/libzmq]
• add GraphicsMagick in addon scientific (optionally used by GMT) ? : http://www.graphicsmagick.org/
• add FFTW in addon scientific (optionally used by GMT) ? : https://www.fftw.org/

[matthieumarrast]

I am testing the migration from Django 3.2 to Django 4.2 as it is the current LTS version.
For postgresql support, mfext is providing version 3.1.4, but django 4.2 expects version 3.1.8 minimum, otherwise it won't start:
django.core.exceptions.ImproperlyConfigured: psycopg version 3.1.8 or newer is required; you have 3.1.4

Ref: https://docs.djangoproject.com/en/4.2/ref/databases/#postgresql-notes

Is it possible to upgrade psycopg to v3.1.8 or newer?

[thebaptiste]

I am testing the migration from Django 3.2 to Django 4.2 as it is the current LTS version. For postgresql support, mfext is providing version 3.1.4, but django 4.2 expects version 3.1.8 minimum, otherwise it won't start: django.core.exceptions.ImproperlyConfigured: psycopg version 3.1.8 or newer is required; you have 3.1.4

Ref: https://docs.djangoproject.com/en/4.2/ref/databases/#postgresql-notes

Is it possible to upgrade psycopg to v3.1.8 or newer?

Done in #1627 (v3.1.9)

[matthieumarrast]

make is not provided by mfext whereas it is an essential tool for metwork.

[matthieumarrast]

For me python-ldap is not a development tool but used in production.
It is provided by layer python3_devtools but we usually install this layer only in development environment, as it is tools for "dev".
Is is possible to include ldap in a standard layer, not devtools ?

[thebaptiste]

For me python-ldap is not a development tool but used in production. It is provided by layer python3_devtools but we usually install this layer only in development environment, as it is tools for "dev". Is is possible to include ldap in a standard layer, not devtools ?

Done by #1689 (python-ldap is moved in layer python3)

[matthieumarrast]

make is not provided by mfext whereas it is an essential tool for metwork.

cf. #1690