Wireshark · Wireshark-dev: Re: [Wireshark-dev] U3 questions/remarks

["Maynard, Chris" <Christopher.Maynard@xxxxxxxxx>]

Sorry, let me clarify my preference.  I don't mean for the binary
executable itself to include the version, but rather the desktop and
menu shortcuts would be sufficient enough for me.  On UN*X, I guess if
there are any symbolic links to the binary, then that might also be
useful as well.
 
The situation is a little more confusing for us (me) because I build
customized versions of Wireshark and differentiate it from the
off-the-shelf version by appending a suffix to the version via
VERSION_EXTRA in config.nmake.  Anyway, to know that the actual
customized version has been installed rather than the off-the-shelf
version, it would help us (me especially) to have the shortcuts named as
"Wireshark-VERSION_MAJOR.VERSION_MINOR.VERSION.MICRO.VERSION_EXTRA",
rather than simply "Wireshark".  Not a big deal though; I'm used to it
the way it is, but if others are also interested, then perhaps it could
be changed.

Thanks,
Chris

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Wednesday, January 31, 2007 1:46 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] U3 questions/remarks

Maynard, Chris wrote:
> Just one comment about the name:  Personally, I prefer the version as
> part of the program name, not just for U3, but I would prefer it for
all
> installs actually.

I would strongly prefer it *NOT* be part of the file name (i.e., *NOT* 
part of the last component of the path name), at least on UN*X, as I 
tend to run Wireshark from the command line.

If that's not what "part of the program name" means (i.e., if it's still

"wireshark" on UN*X), that's OK.

I'd be willing to put up with it being part of the file name if it's 
Windows-only, although there might be Windows users who would find that 
inconvenient - especially for tshark users, as tshark is *intended* to 
be run from the command line or in a script.  Scripts are another place 
where the program has to be invokable with the same name from release to

release.

-----------------------------------------
This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you
are not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data
corruption, interception, tampering, unauthorized amendment and
viruses. We only send and receive emails on the basis that we are
not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.