Wireshark mailing list archives
Re: r45615: Read the program name rather than hardcoding it
From: Anders Broman <a.broman () bredband net>
Date: Wed, 17 Oct 2012 21:35:45 +0200
Guy Harris skrev 2012-10-17 20:04:
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 clearerOn Oct 17, 2012, at 9:37 AM, Anders Broman <a.broman () bredband net> wrote:I will not have the time to rework that now. PF_DIR or program name should come from configure.nmake or something like that on Windows then I suppose.Why not just have it come from epan/filesystem.c, as it does now? What's the problem with hardcoding it? I'll revert the change for now, so that TShark goes back to picking up the standard preferences. At least for protocol and tap preferences, and preferences that apply to Wireshark regardless of the GUI toolkit, we want the same configuration directory for TShark and Wireshark built with GUI toolkit X and Wireshark built with GUI toolkit Y; if there are preferences that only apply to particular GUI toolkits, they should be in separate files, so that, for example, protocol and tap preferences, personal plugins, and the like are shared by everything that uses libwireshark.
that it *is* a internal version. Regards Anders
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- r45615: Read the program name rather than hardcoding it Jakub Zawadzki (Oct 17)
- Re: r45615: Read the program name rather than hardcoding it Anders Broman (Oct 17)
- Re: r45615: Read the program name rather than hardcoding it Guy Harris (Oct 17)
- Re: r45615: Read the program name rather than hardcoding it Anders Broman (Oct 17)
- Re: r45615: Read the program name rather than hardcoding it Guy Harris (Oct 17)
- Re: r45615: Read the program name rather than hardcoding it Anders Broman (Oct 17)
- Re: r45615: Read the program name rather than hardcoding it Guy Harris (Oct 17)
- Re: r45615: Read the program name rather than hardcoding it Anders Broman (Oct 18)
- Re: r45615: Read the program name rather than hardcoding it Guy Harris (Oct 18)
- Re: r45615: Read the program name rather than hardcoding it Anders Broman (Oct 18)
- Re: r45615: Read the program name rather than hardcoding it Guy Harris (Oct 18)
- Re: r45615: Read the program name rather than hardcoding it Guy Harris (Oct 17)
- Re: r45615: Read the program name rather than hardcoding it Anders Broman (Oct 17)