Apt with --root to save OSGEO4W_ROOT in shell environment

[maphew]

Would be nice if apt --root={...} --bits=64 setup saved the OSGEO4W_ROOT var in the shell so that we can just carry on with the next steps in the same session. Otherwise we have to keep re-using --root in every invocation which is a pain, leading to using set osgeo... at the beginning of a session, which leads to the --root parameter being not used, which is another way of saying "essentially useless". ;-)

[amr66]

my way of using apt is either inside a OSGEO-Shell, so the variable is set or i set it by --root. Without that, how do we find the correct directory?

[maphew]

What I meant is I'd like to allow the following usage:

apt --root=x:\path ... setup
    :: on exit root is saved as OS ENV OSGeo4w_root=...
apt find {...}
apt install {...}
apt list 

Instead of the current:

apt --root=x:\path ... setup
apt --root=x:\path find {...}
apt --root=x:\path install {...}
apt --root=x:\path list 

or more commonly:

set osgeo4w_root=x:\path
apt ... setup
apt find {...}
apt install {...}
apt list 

[maphew]

Why bother? I ask myself, where does the urge come from? ...and when I really look it it's simply because I don't like typing ...o4w_...! It's an awkward combination of strokes that slows me down and I often make mistakes on.

[amr66]

So true, but, though i didn't tested it, i think setting a env var in a python script, the variable doen't stay in the calling environment after the python sxcript ended. But may be i'm wrong here...

[amr66]

checked it like this: Win7-Cmd:

echo import os; os.environ["myvar"] = "myval" > env.py
python env.py
echo %myvar%

this shows, that after scripts end, the environment variable myvar does not exist! May be there are other possibilities...