Description

Hello! I came across this issue trying to work around #83 with "volare path" and "volare output" to construct a current PDK path. So you'll see the actual problem is a little silly:

volare path ( points to $HOME/.volare )
volare path --pdk-root=<some pdk root> ( incorrectly points to $HOME/.volare )
PDK_ROOT=<some pdk root> volare path ( correctly points to )

The volare --help command indicates that this should work:

$ volare path --help
Usage: volare path [OPTIONS] [VERSION]

  Prints the path of the volare PDK root.

  If a version is provided over the commandline, it prints the path to this
  version instead.

Options:
  --pdk-root TEXT  Path to the PDK root  [default: /home/petrisko/.volare]
  --pdk TEXT       The PDK family to install  [default: sky130]
  --help           Show this message and exit.

Expected Behavior

volare path --pdk-root=<some pdk root> and PDK_ROOT=<some pdk root> volare path should both point to the same custom PDK root.

Relevant command

$ volare ls --pdk-root=/myhome/.VENV/pdk
$ volare path
$ volare path --pdk-root=/myhome/.VENV/pdk
$ PDK_ROOT=/myhome/.VENV/pdk volare path

Relevant log output

$ volare ls --pdk-root=/myhome/.VENV/pdk
no oauth token found for github.com
In /myhome/.VENV/pdk/volare/sky130/versions:
└── 7519dfb04400f224f140749cda44ee7de6f5e095 (2022.02.10) (enabled)
$ volare path 
/myhome/.volare
$ volare path --pdk-root=/myhome/.VENV/pdk
/myhome/.volare
$ PDK_ROOT=/myhome/.VENV/pdk volare path
/myhome/.VENV/pdk