|author||Balint Reczey <firstname.lastname@example.org>||2014-06-09 14:53:00 +0700|
|committer||Gerald Combs <email@example.com>||2014-06-09 22:02:06 +0000|
Use only dpkg-buildpackage for building .debs
This makes .deb generation not depending on autotools and also removes debian-package target from autotools-generated Makefile. Change-Id: Ia684cd310d85906763af1035fddf39c1fbaed984 Reviewed-on: https://code.wireshark.org/review/2052 Reviewed-by: Evan Huus <firstname.lastname@example.org> Reviewed-by: Gerald Combs <email@example.com>
Diffstat (limited to 'INSTALL')
1 files changed, 12 insertions, 3 deletions
@@ -216,11 +216,10 @@ README.windows for those instructions.
8. Run './wireshark' or './tshark' or ./dumpcap, and make sure things are
working. You must have root privileges in order to capture live data.
-9. Run 'make install'. If you're running a system that supports
- the Apt, RPM, OSX, or System V Release 4 packaging systems, you can
+9./a. Run 'make install'. If you're running a system that supports
+ the RPM, OSX, or System V Release 4 packaging systems, you can
run one of
- make debian-package # Builds a binary package using dpkg
make rpm-package # Builds a binary package using rpm
make srpm-package # Builds a source package using rpm
make svr4-package # Builds a binary package using pkgmk
@@ -229,6 +228,16 @@ README.windows for those instructions.
to make an installable package for your system.
+9/b. If you 're running a system that supports APT (Debian/Ubuntu/etc.)
+ dpkg-buildpackage -us -uc -rfakeroot
+ in the source directory right after extracting of checking out
+ Wireshark's source code. (You don't have to run configure/make/etc.
+ prior to running dpkg-buildpackage)
If you have trouble with the build or installation process, you can
find assistance on the wireshark-users and wireshark-dev mailing lists.
See http://www.wireshark.org/lists/ for details.