Use shared cargo.toml to manage common attributes and dependencies. This way all deps will always be the same version everywhere.
Also:
the license is now specified using proper syntax "MIT OR Apache-2.0"
do not expose dependencies as features
bump all dependencies to latest
on error, geozero-cli will exit with an error code 1
sorted a few lists, e.g. the allow list
FIXME: Still a major issue, possibly for another PR, is how to deal with version bumps. Dependency is currently an absolute mess, similar to geo crates themselves, because geozero-cli, geozero-bench, and even the integration tests for geozero itself depend on an external (!) flatgeobuf crate, which in turn depends on geozero itself. So bumping geozero minor or major version instantly makes the whole project uncompilable!
Use shared cargo.toml to manage common attributes and dependencies. This way all deps will always be the same version everywhere.
Also:
"MIT OR Apache-2.0"
geozero-cli
will exit with an error code 1allow
listFIXME: Still a major issue, possibly for another PR, is how to deal with version bumps. Dependency is currently an absolute mess, similar to geo crates themselves, because
geozero-cli
,geozero-bench
, and even the integration tests forgeozero
itself depend on an external (!)flatgeobuf
crate, which in turn depends ongeozero
itself. So bumpinggeozero
minor or major version instantly makes the whole project uncompilable!