On Sun, Jan 19, 2014 at 12:15 PM, Joerg Mayer <[email protected]> wrote:
> What's the idea behind having a COPYING.txt file on Windows instead
> of a COPYING file?
>
> e.g. ui/gtk/about_dlg.c:
>
> #if defined(_WIN32)
> absolute_path = get_datafile_path("COPYING.txt");
> #else
> absolute_path = get_datafile_path("COPYING");
> #endif
>
> If there is a good reason, how about renaming your COPYING to COPYING.txt
> (and perhaps create a dummy COPYING in case autotools complain)?
>
> Thanks
> Jörg
>
Hi may be historic from Windows installer : (in wireshark.nsi line 48-52)
; NSIS shows Readme files by opening the Readme file with the default
application for
; the file's extension. "README.win32" won't work in most cases, because
extension "win32"
; is usually not associated with an appropriate text editor. We should use
extension "txt"
; for a text file or "html" for an html README file.
I known it is for README file, but in the past, COPYING will be display
with Windows installer
Regards,
--
> Joerg Mayer <[email protected]>
> We are stuck with technology when what we really want is just stuff that
> works. Some say that should read Microsoft instead of technology.
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <[email protected]>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:[email protected]
> ?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <[email protected]>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:[email protected]?subject=unsubscribe