wireshark/debian
Balint Reczey 8ec086a613 Use wildcards for referring to library files in debian/wireshark-common.files
This makes updating debian/wireshark-common.files obsolete when bumping
library versions.

svn path=/trunk/; revision=51016
2013-07-29 17:27:16 +00:00
..
patches As suggest by Balint: 2013-07-15 14:31:35 +00:00
README.source
changelog 1.9.3 → 1.11.0. 2013-04-22 17:59:38 +00:00
compat
control Make Debian package build depend on xdg-utils to let configure detect xdg-open 2013-07-15 17:53:24 +00:00
copyright
dirs
headers-check.c
postinst
pycompat
pyversions
rules Resurrect wsicon32.xpm using 'svn cp' then update it based on 2013-03-29 15:44:14 +00:00
tshark.files
tshark.manpages
watch
wireshark-common.files Use wildcards for referring to library files in debian/wireshark-common.files 2013-07-29 17:27:16 +00:00
wireshark-common.manpages
wireshark-common.shlibs
wireshark-dev.docs
wireshark-dev.files
wireshark-dev.header-files Put wsutil/*.h into the wireshark-dev package (in a blind attempt to fix the debian packaging step). Why do we allow/encourage a wirshark-dev package? IMO Wireshark (C language) development should only be done from the source (a tarball or better yet SVN). 2013-06-25 23:41:06 +00:00
wireshark-dev.manpages
wireshark-dev.prerm
wireshark-root.desktop
wireshark.desktop
wireshark.files
wireshark.manpages
wireshark.menu Resurrect wsicon32.xpm using 'svn cp' then update it based on 2013-03-29 15:44:14 +00:00

README.source

This package uses dpatch in order to apply patches to the upstream 
source.
Patches are stored in debian/patches and their filenames usually end in 
.dpatch .
For further details, see the man pages for dpatch and dpatch-edit-patch.

All commands described below should be run from the top directory of the 
package source tree, unless otherwise stated.

 * To generate the fully patched source, in a form ready for
   editing, that would be built to create Debian packages, run: 

     dpatch apply-all

   Note: This should happen automatically when you run 
   dpkg-source -x on a dpatch source package.

 * To modify the source and save those modifications so that
   they will be applied when building the package, pick a
   suitably informative patch file name, for example
   01_add_README.source_file.dpatch, and then run:

     dpatch-edit-patch 01_add_README.source_file.dpatch

   This will place you in a new shell in a temporary copy of the 
   source tree.  Make your desired modifications to it, and then 
   exit the shell to create the patch file containing them (this 
   file will appear in debian/patches).

 * To remove source modifications that are currently being
   applied when building the package, run:

     dpatch unapply-all