Guy Harris skrev 2012-10-17 22:13:
On Oct 17, 2012, at 12:35 PM, Anders Broman <a.broman@xxxxxxxxxxxx> wrote:
One use case is a internal version which would be nice to be able to install co-existing with a
release version with separate profiles and preferences. Having a different program name makes it clearer
that it *is* a internal version.
...but what's different about it isn't its name, what's different about it is the version.
?
The the dissectors would be different...
Furthermore, there isn't even an "it" - there are at least two "it"s, Wireshark and TShark. For that use case, what would the internal versions of Wireshark and TShark be called? If it'd be "wireshark-XXX" and "tshark-XXX" for some value of "XXX", perhaps the preference directory should be {Wireshark,.wireshark}-XXX, although there might also be cases where the name is different but the preferences directory should be shared, so perhaps the two should be configured independently.
On windows the program installation dir, short cuts, registry entries
and installer "paths" contains the name Wireshark if you do multiple
installations of Wireshark by defining different installation dirs
application
data would still be shared and uninstalling one version might rip the
personal settings etc out - that might be considered a bug.
On Windows if you want to run the command line tools you would have to
run the from the program dir so in this case having different "program"
names would leave you with two independent installations including
personal settings. So running Tshark etc from the program dir of
programname1 vs programname2 would give the desired result I think.
So on windows the name of the cli tools can be the same in program name1
and program name 2.
But to cover all cases would we like to be able to configure the name of
tshark wireshark and the personal settings dir? the other tools are
perhaps unlikely to be customized? or shouldn't we support name change
at all?
Best regards
Anders
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe