This is not exactly a bug but more of a remark about the SEPAL environment.
Applications are living in a Linux environment that is already hydrated with many libs packages and softwares. That is awesome as anybody can jump here and start coding geospatial stuff without thinking of the burden of installing some of the most *%£$$$ linux packages I've ever seen.
The main issue here is every time SEPAL is rebuilt, the version of one (or both) of these package is suceptible to change putting at risk all the libs that are depending on it. this list is not exhaustive but in our requirements there is rgdal, localtile (until I finish working on https://github.com/girder/large_image/issues/898), gdal, pygdal, pyproj ... etc
Do we really need to have the latest one ?
Could we instead pin them to a specific version and update them once in a while to ensure that everything in SEPAL continues working until we really want to change?
cdanielw
commented
1 year ago
This is not exactly a bug but more of a remark about the SEPAL environment. Applications are living in a Linux environment that is already hydrated with many libs packages and softwares. That is awesome as anybody can jump here and start coding geospatial stuff without thinking of the burden of installing some of the most *%£$$$ linux packages I've ever seen.
I'm of course pointing at GDAL and PROJ.
The main issue here is every time SEPAL is rebuilt, the version of one (or both) of these package is suceptible to change putting at risk all the libs that are depending on it. this list is not exhaustive but in our requirements there is
rgdal,localtile(until I finish working on https://github.com/girder/large_image/issues/898),gdal,pygdal,pyproj... etcDo we really need to have the latest one ? Could we instead pin them to a specific version and update them once in a while to ensure that everything in SEPAL continues working until we really want to change?