On Jul 31, 2014, at 1:18 AM, Bálint Réczey bal...@balintreczey.hu wrote:
Since the files stored in git are enough for building Wireshark on
every platform we support,
...as long as the user has Flex and Perl and Python and automake and autoconf
and libtool (and possibly other tools)
On Jul 31, 2014, at 1:18 AM, Bálint Réczey bal...@balintreczey.hu wrote:
Since the files stored in git are enough for building Wireshark on
every platform we support
So we shouldn't bother generating or shipping tarballs at all, just say check
out this from git if you want the 1.X.Y source?
2014-07-31 10:32 GMT+02:00 Guy Harris g...@alum.mit.edu:
On Jul 31, 2014, at 1:18 AM, Bálint Réczey bal...@balintreczey.hu wrote:
Since the files stored in git are enough for building Wireshark on
every platform we support
So we shouldn't bother generating or shipping tarballs at all, just
On Wednesday 30 July 2014 14:35:06 Gerald Combs wrote:
After comparing the tarballs generated by make dist and
git-export-release.sh I have to agree. Both have issues but the dist
tarball will build according to our documentation on Linux, Windows, and
OS X.
make dist is missing:
- Quite
2014-07-31 12:34 GMT+02:00 Peter Wu pe...@lekensteyn.nl:
On Wednesday 30 July 2014 14:35:06 Gerald Combs wrote:
After comparing the tarballs generated by make dist and
git-export-release.sh I have to agree. Both have issues but the dist
tarball will build according to our documentation on
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu wrote:
2014-07-31 12:34 GMT+02:00 Peter Wu pe...@lekensteyn.nl:
On Wednesday 30 July 2014 14:35:06 Gerald Combs wrote:
After comparing the tarballs generated by make dist and
git-export-release.sh I have to agree. Both have issues
On Thu, Jul 31, 2014 at 12:34:18PM +0200, Peter Wu wrote:
Another thing to consider is the availability of cmake which does not require
additional files in a distribution tarball like autotools. If all platforms
support cmake, what about dropping the autotools-generated stuff?
Oh no! Now you
On 07/31/14 06:42, Bálint Réczey wrote:
2014-07-31 12:34 GMT+02:00 Peter Wu pe...@lekensteyn.nl:
Another thing to consider is the availability of cmake which does not require
additional files in a distribution tarball like autotools. If all platforms
support cmake, what about dropping the
On 7/31/14 6:08 AM, Graham Bloice wrote:
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu
mailto:bal...@balintreczey.hu wrote:
+1 for dropping autotools in favor of CMake. CMake already covers all
my use cases.
Same here except for Windows. I've been doing most of my Qt
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote:
On 7/31/14 6:08 AM, Graham Bloice wrote:
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu
mailto:bal...@balintreczey.hu wrote:
+1 for dropping autotools in favor of CMake. CMake already covers all
my use
This issue has been bugging me for a while, but I also haven't been able to
come up with a satisfactory solution.
On Thu, Jul 31, 2014 at 4:56 PM, Wireshark code review
code-review-do-not-re...@wireshark.org wrote:
URL:
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote:
On 7/31/14 6:08 AM, Graham Bloice wrote:
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu
mailto:bal...@balintreczey.hu wrote:
+1 for dropping autotools in favor of CMake. CMake already covers all
my use
On 31 July 2014 22:14, Graham Bloice graham.blo...@trihedral.com wrote:
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org wrote:
On 7/31/14 6:08 AM, Graham Bloice wrote:
On 31 July 2014 11:42, Bálint Réczey bal...@balintreczey.hu
mailto:bal...@balintreczey.hu wrote:
+1 for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm proud to announce the release of Wireshark 1.12.0.
__
What is Wireshark?
Wireshark is the world's most popular network protocol
analyzer. It is used for troubleshooting,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm proud to announce the release of Wireshark 1.10.9.
__
What is Wireshark?
Wireshark is the world's most popular network protocol
analyzer. It is used for troubleshooting,
On Thu, Jul 31, 2014 at 08:56:31PM +, Wireshark code review wrote:
URL:
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=43a81b61395358d93a3f859e9058dfd7ecc39a7e
Submitter: Guy Harris (g...@alum.mit.edu)
Changed: branch: master
Repository: wireshark
Commits:
On Thu, Jul 31, 2014 at 05:11:59PM -0400, Evan Huus wrote:
This issue has been bugging me for a while, but I also haven't been able to
come up with a satisfactory solution.
I hope to look into this soon ('ish)
Ciao
Jörg
--
Joerg Mayer
On Thursday 31 July 2014 17:11:59 Evan Huus wrote:
This issue has been bugging me for a while, but I also haven't been able to
come up with a satisfactory solution.
Oh my, that filesystem.c code is really ugly and relying on a lot of
assumptions. Why does it need to distinguish build dirs from
On Jul 31, 2014, at 2:51 PM, Gerald Combs ger...@wireshark.org wrote:
Removed Dissectors
* The ASN1 plugin has been removed as it's deemed obsolete.
The source is still in the source tree; should we get rid of it?
* The GNM dissector has been removed as it was never used.
It's
On 7/31/14 2:19 PM, Graham Bloice wrote:
On 31 July 2014 22:14, Graham Bloice graham.blo...@trihedral.com
mailto:graham.blo...@trihedral.com wrote:
On 31 July 2014 17:34, Gerald Combs ger...@wireshark.org
mailto:ger...@wireshark.org wrote:
On 7/31/14 6:08 AM, Graham Bloice
On Jul 31, 2014, at 3:21 PM, Jeff Morriss jeff.morriss...@gmail.com wrote:
The commit message there says it was removed because it was never used.
Never used in what sense?
Nobody ever read a capture file that used it?
Or nothing will ever use the OIDs for which it registers?
On 07/31/14 04:27, Wireshark code review wrote:
URL:
https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=7f3d97c669970538158d01d33ed5d494477d2378
Submitter: Guy Harris (g...@alum.mit.edu)
Changed: branch: master
Repository: wireshark
Commits:
7f3d97c by Guy Harris
On Jul 31, 2014, at 3:11 PM, Peter Wu pe...@lekensteyn.nl wrote:
On Thursday 31 July 2014 17:11:59 Evan Huus wrote:
This issue has been bugging me for a while, but I also haven't been able to
come up with a satisfactory solution.
Oh my, that filesystem.c code is really ugly and relying on
FWIW this issue also makes it impossible to run parts of the test suite
from an out-of-tree build, which can be problematic.
On Thu, Jul 31, 2014 at 4:56 PM, Wireshark code review
code-review-do-not-re...@wireshark.org wrote:
URL:
24 matches
Mail list logo
