From: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
---|---|
To: | Svensson Peter <peter(dot)svensson(at)smhi(dot)se>, "pgsql-pkg-yum(at)postgresql(dot)org" <pgsql-pkg-yum(at)postgresql(dot)org> |
Subject: | Re: SV: SV: gdal30 and Rhel 8.4 dependency problem |
Date: | 2021-05-28 07:13:34 |
Message-ID: | c7a4c6fb62e6eef089af4083637b312656606b36.camel@gunduz.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-yum |
Hi,
On Fri, 2021-05-28 at 06:23 +0000, Svensson Peter wrote:
> We use in this combination proj70 , geos38 and postgis24
Ahh, that now makes sense (see below) .
> But gdal30 requires libproj.so.19()(64bit) so I think even proj72 will
> work.
My very original plan was to support a single GeOS/GDAL/PROJ
combination across all PostGIS installations, which miserably failed
after PROJ 8.0:
checking for proj_api.h... no
configure: error: could not find proj_api.h - you may need to specify
the directory of a PROJ.4 installation using --with-projdir
Upstream patched 3.0 and 3.1 for that, and that is why users of the
recent versions actually have no issues.
> and gdal30-libs requires libgeos_c.so.1()(64bit) so even geos39 are
> possible
>
> postgis24 requires libgdal.so.26()(64bit)
I even removed gdal30 spec files from pgdg repos a few months ago :-)
Let me see what I can do. Either I will solve the problem on the
packaging side, or will just as users to add these packages to
exclude=... list, so that yum/dnf update won't complain.
Regards,
--
Devrim Gündüz
Open Source Solution Architect, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2021-06-01 23:39:25 | Re: postgis for beta releases |
Previous Message | Svensson Peter | 2021-05-28 06:23:49 | SV: SV: gdal30 and Rhel 8.4 dependency problem |