Re: [Wireshark-dev] What is the history and status of PCAP Next Generation?

2013-10-09 Thread Jasper Bongertz
Sorry to answer this late; I saw this email a week ago but didn't manage to reply - the todo got swapped out but never swapped in again. Graham gave me a heads up (that I didn't see until now, either, *sigh*), so here I go. Q2: What is the status of pcap-ng? * it works fine, everyone's

Re: [Wireshark-dev] 1.11.0 release

2013-10-09 Thread Bálint Réczey
Hi Gerald, 2013/10/8 Gerald Combs ger...@wireshark.org: I've scheduled the release of 1.11.0 for next Tuesday, October 15. Corrections and additions for the release notes are welcome. Unfortunately the transitional state of our UI will be reflected in the release packages: Windows 32-bit:

Re: [Wireshark-dev] 1.11.0 release

2013-10-09 Thread Guy Harris
On Oct 9, 2013, at 2:47 AM, Bálint Réczey bal...@balintreczey.hu wrote: How about dropping the automake based and nmake based makefile systems and replacing both with CMake? So do you propose that people who are building from source only because they don't have binary packages available for

Re: [Wireshark-dev] 1.11.0 release

2013-10-09 Thread Guy Harris
On Oct 8, 2013, at 12:21 PM, Gerald Combs ger...@wireshark.org wrote: I've scheduled the release of 1.11.0 for next Tuesday, October 15. Meaning we'll no longer be offering a development release that's older than the current stable release? (We should probably drop the development release

Re: [Wireshark-dev] 1.11.0 release

2013-10-09 Thread Graham Bloice
On 9 October 2013 11:21, Bálint Réczey bal...@balintreczey.hu wrote: 2013/10/9 Guy Harris g...@alum.mit.edu: On Oct 9, 2013, at 2:47 AM, Bálint Réczey bal...@balintreczey.hu wrote: How about dropping the automake based and nmake based makefile systems and replacing both with CMake?

Re: [Wireshark-dev] 1.11.0 release

2013-10-09 Thread Guy Harris
On Oct 9, 2013, at 3:21 AM, Bálint Réczey bal...@balintreczey.hu wrote: Building Wireshark already needs way more tools than just make and a C compiler. Perhaps we should fix that, so that the release tarball includes all generated source. I'd prefer not to require Flex, yacc/Bison, Perl,

Re: [Wireshark-dev] 1.11.0 release

2013-10-09 Thread Bálint Réczey
Hi Guy, 2013/10/9 Guy Harris g...@alum.mit.edu: On Oct 9, 2013, at 3:21 AM, Bálint Réczey bal...@balintreczey.hu wrote: Building Wireshark already needs way more tools than just make and a C compiler. Perhaps we should fix that, so that the release tarball includes all generated source.

Re: [Wireshark-dev] [Wireshark-commits] rev 52462: /trunk/ /trunk/docbook/: release-notes.asciidoc /trunk/epan/: expert.c packet.c proto.c show_exception.c /trunk/ui/gtk/: main_menubar.c prefs_dlg.c /

2013-10-09 Thread Joerg Mayer
On Wed, Oct 09, 2013 at 12:56:21PM +, mm...@wireshark.org wrote: http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=revrevision=52462 User: mmann Date: 2013/10/09 12:56 PM Log: Prefix all Wireshark application specific display filters with a _ws. to distinguish them from dissector

Re: [Wireshark-dev] 1.11.0 release

2013-10-09 Thread Joerg Mayer
On Wed, Oct 09, 2013 at 03:15:41PM +0200, Bálint Réczey wrote: According to our CMakeList.txt it will be: ... project(Wireshark C CXX) cmake_minimum_required(VERSION 2.6) set(CMAKE_BACKWARDS_COMPATIBILITY 2.6) ... Unless you want to build with Qt5: