docker: build gdal-grass with grass in working condition#5115
docker: build gdal-grass with grass in working condition#5115wenzeslaus merged 3 commits intoOSGeo:mainfrom
Conversation
|
So that line breaks grass? Is this now in sync with Ubuntu? |
There are copying operations later on, which "fix" that. Without being able to test locally, this solution seems the best one.
The Dockerfiles are differently organised. So this (seemingly) doesn't affect the other Dockers. |
|
Shall we try this out? |
I guess I just don't understand the current Docker enough to know why is that needed. |
|
Is there a problem preventing to try locally? Like does it work on macOS too? |
Probably not.
Don't know. I never tried the Docker road. Couple of years ago, looking at it, I was hold back because of the space required. Then never really felt the need to. |
|
Ahhrr, builds but not working properly: |
Partial, manual backport of: OSGeo#5106 1c1d01d OSGeo#5108 6b652b6 OSGeo#5115 d657e54 OSGeo#5137 7bfe274
Partial, manual backport of: OSGeo#5106 1c1d01d OSGeo#5108 6b652b6 OSGeo#5115 d657e54 OSGeo#5137 7bfe274
Partial, manual backport of: OSGeo#5106 1c1d01d OSGeo#5108 6b652b6 OSGeo#5115 d657e54 OSGeo#5137 7bfe274
#5111 was not enough to fix the Alpine docker build.
gdal-grassCMake config usesgrassfor setting paths and requires a working state of grass.This was not the case because of:
grass/docker/alpine/Dockerfile
Line 171 in d3993e2
just before the gdal-grass build started.
This moves the gdal-grass build immediately after grass is built, this hopefully will solve this issue.