Arch Linux User Repository

@all

In case you wondered, you can fetch the `grass7' PKGBUILD that `gdal-grass' depends on from my GitLab place - https://gitlab.com/tutturu/grass7_pkgbuild.

I'm not allowed to upload `grass7' to AUR, because it was rated not different enough from `grass'. Anyway, it's different enough to make a difference in practice ;).

@dickoa
> I think that you need to build gdal without grass support

GDAL in Arch repository comes without GRASS support. There's no need to rebuild it before building gdal-grass. See this:

Before installing gdal-grass:

$ gdalinfo --formats | grep -i grass
GRASSASCIIGrid -raster- (rov): GRASS ASCII Grid
$ ogrinfo --formats | grep -i grass
(no output)

After installing gdal-grass:

$ gdalinfo --formats | grep -i grass
GRASS -raster- (ro): GRASS Rasters (5.7+)
GRASSASCIIGrid -raster- (rov): GRASS ASCII Grid
$ ogrinfo --formats | grep -i grass
OGR_GRASS -vector- (ro): GRASS Vectors (5.7+)

Or did you mean something else?

You are correct about the extra `/' in --prefix. I'll remove it in a next release. It doesn't do any harm though - GNU/Linux doesn't mind double leading slash `//' in a path. It treats it identical to a single leading slash `/'.

Nice work but to make it work, I think that you need to build gdal without grass support according to https://grasswiki.osgeo.org/wiki/Compile_and_install_GDAL-GRASS_plugin

On line 20 of your PKGBUILD you have:
--prefix=/${pkgdir}/usr

I am not sure but I think that it should be replaced by (without "/" at the beginning):
--prefix=${pkgdir}/usr

Thanks again

@all

In case you wondered, you can fetch the `grass7' PKGBUILD that `gdal-grass' depends on from my GitLab place - https://gitlab.com/tutturu/grass7_pkgbuild.

I'm not allowed to upload `grass7' to AUR, because it was rated not different enough from `grass'. Anyway, it's different enough to make a difference in practice ;).