I did an analysis of the top-level source files, to see the groupings.
*Small Programs*
capinfos.c - for capinfos
dftest..c - for dftest
editcap.c - for editcap
mergecap.c - for mergecap
randpkt.c - for randpkt
rawshark.c - for rawshark
text2pcap.c & text2pcap-scanner.c (generated) - for text2pcap
On Mar 8, 2012, at 12:26 AM, Guy Harris wrote:
>> alert_box.c
>
> Oops, that one belongs in the ui subdirectory, as it's only used by
> Wireshark, not TShark or rawshark; I'll work on moving it there.
Done.
___
Sent via:
Gilbert Ramirez wrote:
The existence of so many source files in the top-level directory of the
Wireshark source distribution bothers me. I would love to be able to
"ls" the top-level directory and not have it scroll off my screen.
As a general comment: +1/yes please!
_
Guy Harris wrote:
On Mar 7, 2012, at 9:07 PM, Gilbert Ramirez wrote:
I also feel that the directories that distribute data files (radius, dtds, idl), should
all be moved under another new directory, perhaps "definitions", but I know
less about those files.
One advantage of having them in the
On Mar 7, 2012, at 9:07 PM, Gilbert Ramirez wrote:
> With this in mind, and by analyzing the groupings in Makefile.common, I'd
> like to recommend the following movements:
>
> Create new directory called shark, to contain files common, or almost common,
> to the analyzer applications (wireshar
On Wed, Mar 07, 2012 at 09:07:12PM -0800, Gilbert Ramirez wrote:
> The existence of so many source files in the top-level directory of the
> Wireshark source distribution bothers me. I would love to be able to "ls"
> the top-level directory and not have it scroll off my screen.
>
> I have diagramm
The existence of so many source files in the top-level directory of the
Wireshark source distribution bothers me. I would love to be able to "ls"
the top-level directory and not have it scroll off my screen.
I have diagrammed the current Wireshark source directory hierarchy at:
http://www.gliffy.
