Skip to content

Commit c6e345f

Browse files
committed
Improve README re json breaking change
1 parent 94b723f commit c6e345f

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

README.md

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,18 @@ Minimum versions supported:
3333
* osm2pgsql 1.4.2+ --> commit 94dae34 or newer
3434

3535

36-
### :warning: Breaking change :warning:
37-
38-
The osm2pgsql project added built-in JSON support after v1.4.2 ([commit](https://github.com/openstreetmap/osm2pgsql/commit/94dae34b7aa1463339cdb6768d28a6e8ee53ef65)).
39-
Currently this change is not in a tagged release, only the latest `master` branch.
40-
Install osm2pgsql from source to use the current `main` branch of PgOSM-Flex.
41-
42-
To use osm2pgsql v1.4.2, use PgOSM-Flex v0.1.5.
36+
### :warning: Breaking change
37+
38+
The osm2pgsql project added built-in JSON support after the tagged
39+
v1.4.2 release. This change ([commit](https://github.com/openstreetmap/osm2pgsql/commit/94dae34b7aa1463339cdb6768d28a6e8ee53ef65))
40+
is not yet in a tagged release of osm2pgsql, only the
41+
latest `master` branch.
42+
43+
This is only a concern when running on a server where you install osm2pgsql
44+
from a package manager. Following the instructions in
45+
[MANUAL-STEPS-RUN.md](MANUAL-STEPS-RUN.md) installs the latest
46+
version of osm2pgsql from source and avoids this issue.
47+
Also, using the PgOSM Flex Docker image makes this a non-issue.
4348

4449

4550
## PgOSM via Docker

0 commit comments

Comments
 (0)