1 | Source: libtrace4 |
---|
2 | Priority: optional |
---|
3 | Maintainer: Brad Cowie <brad@wand.net.nz> |
---|
4 | Build-Depends: debhelper (>= 9), dh-autoreconf, |
---|
5 | libpcap-dev, zlib1g-dev, flex, bison, doxygen, liblzma-dev, graphviz, |
---|
6 | libncurses5-dev, libbz2-dev, libssl-dev, libwandio1-dev, libwandder1-dev, |
---|
7 | dpdk-dev, libnuma-dev |
---|
8 | Standards-Version: 4.1.3 |
---|
9 | Section: libs |
---|
10 | Homepage: http://research.wand.net.nz/software/libtrace.php |
---|
11 | |
---|
12 | Package: libtrace4-dev |
---|
13 | Section: libdevel |
---|
14 | Architecture: any |
---|
15 | Depends: libtrace4 (= ${binary:Version}), ${misc:Depends} |
---|
16 | Provides: libtrace-dev |
---|
17 | Conflicts: libtrace-dev, libpacketdump3-dev |
---|
18 | Replaces: libtrace-dev |
---|
19 | Description: development headers for the libtrace network processing library |
---|
20 | This package contains development headers and other ancillary files for |
---|
21 | the libtrace library. |
---|
22 | . |
---|
23 | libtrace is a library for trace processing. It supports multiple input |
---|
24 | methods, including device capture, raw and gz-compressed trace, and sockets; |
---|
25 | and multiple input formats, including pcap and DAG. |
---|
26 | . |
---|
27 | libtrace is developed by the WAND Network Research Group at Waikato |
---|
28 | University in New Zealand. |
---|
29 | |
---|
30 | Package: libtrace4 |
---|
31 | Section: libs |
---|
32 | Architecture: any |
---|
33 | Depends: ${shlibs:Depends}, ${misc:Depends} |
---|
34 | Provides: libtrace |
---|
35 | Conflicts: libtrace, libtrace3 |
---|
36 | Replaces: libtrace3 |
---|
37 | Description: network trace processing library supporting many input formats |
---|
38 | libtrace is a library for trace processing. It supports multiple input |
---|
39 | methods, including device capture, raw and gz-compressed trace, and sockets; |
---|
40 | and multiple input formats. |
---|
41 | . |
---|
42 | libtrace is developed by the WAND Network Research Group at Waikato |
---|
43 | University in New Zealand. |
---|
44 | |
---|
45 | Package: libpacketdump4-dev |
---|
46 | Section: libdevel |
---|
47 | Architecture: any |
---|
48 | Depends: libpacketdump4 (= ${binary:Version}), ${misc:Depends} |
---|
49 | Provides: libpacketdump-dev |
---|
50 | Conflicts: libpacketdump-dev |
---|
51 | Replaces: libpacketdump-dev |
---|
52 | Description: development headers for the libpacketdump library |
---|
53 | This package contains development headers and other ancillary files for |
---|
54 | the libpacketdump library. |
---|
55 | . |
---|
56 | libpacketdump provides a library which can parse packets and display the |
---|
57 | packet contents in a nice human-readable form. The output is similar to that |
---|
58 | produced by tcpdump, although the formatting is somewhat more verbose. |
---|
59 | . |
---|
60 | libpacketdump is developed by the WAND Network Research Group at Waikato |
---|
61 | University in New Zealand. |
---|
62 | |
---|
63 | Package: libpacketdump4 |
---|
64 | Section: libs |
---|
65 | Architecture: any |
---|
66 | Depends: ${shlibs:Depends}, ${misc:Depends} |
---|
67 | Provides: libpacketdump |
---|
68 | Conflicts: libpacketdump, libpacketdump3 |
---|
69 | Replaces: libpacketdump3 |
---|
70 | Description: network packet parsing and human-readable display library |
---|
71 | libpacketdump provides a library which can parse packets and display the |
---|
72 | packet contents in a nice human-readable form. The output is similar to that |
---|
73 | produced by tcpdump, although the formatting is somewhat more verbose. |
---|
74 | . |
---|
75 | libpacketdump is developed by the WAND Network Research Group at Waikato |
---|
76 | University in New Zealand. |
---|
77 | |
---|
78 | Package: libtrace4-tools |
---|
79 | Section: net |
---|
80 | Architecture: any |
---|
81 | Depends: ${shlibs:Depends}, ${misc:Depends} |
---|
82 | Conflicts: libtrace-tools |
---|
83 | Replaces: libtrace-tools |
---|
84 | Description: helper utilities for use with the libtrace process library |
---|
85 | libtrace is a library for trace processing. These tools perform many common |
---|
86 | tasks that are required when analysing and manipulating network traces. |
---|
87 | . |
---|
88 | Multiple input methods and formats are supported including device capture, |
---|
89 | raw and gz-compressed traces, and sockets. |
---|
90 | . |
---|
91 | libtrace is developed by the WAND Network Research Group at Waikato |
---|
92 | University in New Zealand. |
---|