Update README.md #143
Update README.md #143
Conversation
Add binary distributions list
|
Wow, this is really cool! If I'm understanding the thread correctly, they are modifying the extension such that it is linking against system-installed h3 core. What is their process regarding updates? Let's say uber releases h3 core v5, and I release h3-pg v5 which depends upon core v5. Will they release updates in lockstep? Do they have some kind of release schedule? Anyway, thank you very much, I'll look a bit more into it and merge one of the next days! |
|
This explanation is kinda long, but hopefully understandable
The way I understand (Devrim, yum.postgresql.org packager often builds dependencies himself if he feels upstream is too old and puts them on pgdg-depends, thus Redhat derivatives often run withe newest GEOS and GDAL for example and probably have no issue using the version of h3 you package. Sadly apt.postgresql.org (Debian/Ubuntu, always get their dependencies from main repo, thus why they pulled h3 from the main repos. Even more sad, these dependencies tend to be older for older systems. On the plus side, I guess it means less friction and smoother install for most people though they'll gripe about the missing functionality. But on the negative, if main repo for a distro no longer carries the h3 you rely on, it means they can not ship your newer for that Ubuntu/Debian distro. This sadly I have faced on PostGIS side. E.g. when we upped GEOS dependency in PostGIS 3.5, I'm sure we are saying good bye to some older Ubuntu/Debian release versions. As far as the frequency of releases of both Yum and Apt. They tend to release as soon as you release for at least the latest PostgreSQL version. But that all depends on major/minor etc. E.g. they will release a micro for all supported PostgreSQL versions, but only a major/minor for latest PostgreSQL version. That's why I always run around packages I use or plan to package to make sure they work with in-development releases, to make sure they can be packaged. On the windows side, which I manage, I try to ship all PostGIS related (or that depend on PostGIS) that I feel are gaining popularity and are stable enough to be packaged. In my case, since I build all dependencies from scratch, I have no concerns about any repo what they are doing, beyond what libraries EDB (packager for PostgreSQL on windows) ships (like ssl, zlib, xml). So I'll build with latest stable GEOS, (sometimes GDAL, though I fall behind on that since the version is not that important for most uses), and H3 whatever you include. I also build only the latest stable PostGIS and other PostGIS related spatial extension for all versions of PostgreSQL that can support it. So that means PostGIS 3.4 bundle supports (PostgreSQL 12-16) and PostGIS 3.5 will likely support (PostgreSQL 12-17) unless we drop 12, in which case will be (PostgreSQL 13-17). And since Windows, as much as people like to complain about it, all support versions work with anything, will be for at least the supported versions of Windows that PostgreSQL supports. Which tends to have a 12-15 year cycle. |
yum should use sudo as well. Reduce instructions for Debian/Ubuntu since the other instructions of how to set up are already explained on the postgresql.org site linked
More cleanup. Reduce instructions for Debian/Ubuntu, since those are already linked. On Windows mentioned the PostgreSQL windows distribution.
Forgot Centos 8 not supported. Just Rocky
more cleanup and add links to yum and apt postgresql.org
Fix typo
|
Sorry about all the changes. Found typos and had to clarify some stuff. |
|
Good changes! And thanks for the explanation :-) This should make things much easier for newcomers. |
Add binary distributions list
I asked PGDG yum and apt groups to start carrying it, and they obliged, very quickly
https://www.postgresql.org/message-id/ZUgQfTASY2QQToYX%40msg.df7cb.de
I was already carrying for windows, so also added that to the list.