I think the reason for that was to put as much functionality as posible behind the DXROOT environment variable, and have minimal functionality - just applying DXROOT - in the common public place - eg. /usr/local/bin or /usr/bin. I doubt there are a lot of people using multiple DXROOTs, so I don't see a problem with combining them for simplicity's sake. Greg
- [opendx-dev] Why dxworker and dx? David Thompson
- [opendx-dev] Can opendx be wrapped in python? Chen Fu
- Re: [opendx-dev] Can opendx be wrapped in pyt... David Thompson
- [opendx-dev] MacOS 10.2.5 runtime error Richard Gillilan
- Re: [opendx-dev] MacOS 10.2.5 runtime... Matthew Bettencourt
- Re: [opendx-dev] MacOS 10.2.5 ru... Richard Gillilan
- Re: [opendx-dev] Why dxworker and dx? Gregory D Abram
