If the user tries to save a capture file atop a file that has all its
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Sat, 2 Jun 2012 18:53:13 +0000 (18:53 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Sat, 2 Jun 2012 18:53:13 +0000 (18:53 +0000)
commitb022f287c5b550d87e97a643ee81d5a0cfad9051
tree17f79825410c1847824774adca2381fa2a113ca5
parent9d894d90c4a874198cdbc99aecadea8ce910d6d0
If the user tries to save a capture file atop a file that has all its
write bits turned off or, on 4.4-Lite-based systems, has its "user
immutable" bit turned on, ask them if they really want to overwrite the
file (as those are both used to say "this file is precious, don't let me
easily accidentally trash it") and, if the "user immutable" bit is set,
turn it off first so that the move in the "safe save" won't fail.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@43006 f5534014-38df-0310-8fa8-9805f1628bb7
acinclude.m4
configure.in
ui/gtk/capture_file_dlg.c