On 2022-02-11 3:48 p.m., Howard Butler wrote:
On Feb 11, 2022, at 1:41 PM, Jeff McKenna
<jmcke...@gatewaygeomatics.com <mailto:jmcke...@gatewaygeomatics.com>>
wrote:
Unfortunately this issue comes up very often, as you said, so much of
our stack relies heavily on environment variables. My hope is that in
the long run, the ini-style of settings can help battle this Windows
Server x64 issue (yes googling this does return many
unproven/non-reproducible reports for other projects, very disheartening).
The frustrations of how to pass environment variables in different
computing environments is an issue that's orthogonal to how GDAL
expresses configuration through environment variables. I get that the
rules of environment variable resolution can be quite bespoke depending
on the computing platform and environment you are operating on, but it's
not legit to say "environment variables don't always work for me, we
should do config files, but I don't have a reproducible test case to
show that"
I agree here. But it's important to share and give thoughts, and by
having an open discussion I'm sure other packagers will keep an eye open
for such mysterious issues on Windows Server x64 with cacert environment
variables. (I hope to never see the issue reported again to me, ha)
-jeff
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
