Sake Blok <sake@...> writes:
> > Since 1.10 is the last version that will support U3[1] though, we should
> > probably change the name of that environment variable to something else. My
> > vote would be to use WS_APPDATA, and I'll likely change it to that in the
> > trunk unless there are any objections.
>
> +1
For anyone who might be following this thread who is not on the
wireshark-commits mailing list ...
As noted in the commit message for r52022[1], I chose WIRESHARK_APPDATA
instead of WS_DATA, because most of the other Wireshark-related environment
variables were prefixed with WIRESHARK_ and not WS_. And Jeff updated the
man pages that I missed with his commit in r52024[2].
Also, I didn't remove the U3-related environment variables at this time, so
currently U3_APP_DATA_PATH still works as well, although the new
WIRESHARK_APPDATA will override U3_APP_DATA_PATH if they both happen to be
set. I left U3_APP_DATA_PATH (as well as U3_DEVICE_EXEC_PATH and
U3_DEVICE_DOCUMENT_PATH) undocumented, as I expect them to be removed anyway
before 1.12 is released.
- Chris
[1]: http://anonsvn.wireshark.org/viewvc?revision=52022&view=revision
[2]: http://anonsvn.wireshark.org/viewvc?revision=52024&view=revision