From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: postgis |
Date: | 2022-07-20 14:57:58 |
Message-ID: | CAKFQuwY_NvHuXTNqJsuWZjPx2DVMF4drwPQUiUQzn9qf57Ninw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wednesday, July 20, 2022, Marc Millas <marc(dot)millas(at)mokadb(dot)com> wrote:
> Thanks for your answer.
> I would like to avoid compiling as much as possible.
> I know that postgis 3.2.1 is available and does install without pb. but..
> That db run an app which is very long to test, so I need to stick to a
> postgis 3.0.x
>
I’m not particularly fluent here but working from the PostGIS project
homepage and into the linked package archives I do not see where what you
want exists. It doesn’t seem like the 3.0.x series is being kept
up-to-date in packaged form.
But you may want to use PostGIS support channels to have a better chance at
getting confirmation/help rather than here.
My general impression is that the packaging, at least for Debian, doesn’t
actually understand how the PostGIS project handles versioning support.
But i may be missing something as I’m doing this web-only and
apt.postgresql.org is basically impossible to inspect on the web.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2022-07-20 15:07:54 | Re: Batch process |
Previous Message | Adrian Klaver | 2022-07-20 14:52:35 | Re: Batch process |