[Python-apps-commits] r3657 - in packages/lfm/trunk/debian (README.source)

dktrkranz at users.alioth.debian.org dktrkranz at users.alioth.debian.org
Tue Sep 1 22:23:44 UTC 2009


    Date: Tuesday, September 1, 2009 @ 22:23:43
  Author: dktrkranz
Revision: 3657

Replace DEBIAN.source with the one specific for quilt

Modified:
  packages/lfm/trunk/debian/README.source

Modified: packages/lfm/trunk/debian/README.source
===================================================================
--- packages/lfm/trunk/debian/README.source	2009-09-01 22:22:20 UTC (rev 3656)
+++ packages/lfm/trunk/debian/README.source	2009-09-01 22:23:43 UTC (rev 3657)
@@ -1,35 +1,57 @@
-This package uses CDBS (and therefore simple-patchsys.mk) in order to 
-apply patches to the upstream source. Patches are stored in 
-debian/patches and their filenames usually end in .patch or .diff .
-For further details, see the man page for cdbs-edit-patch.
+This package uses quilt to manage all modifications to the upstream
+source.  Changes are stored in the source package as diffs in
+debian/patches and applied during the build.
 
-All commands described below should be run from the top directory of the 
-package source tree, unless otherwise stated.
+To configure quilt to use debian/patches instead of patches, you want
+either to export QUILT_PATCHES=debian/patches in your environment
+or use this snippet in your ~/.quiltrc:
 
- * To generate the fully patched source, in a form ready for
-   editing, that would be built to create Debian packages, run: 
+    for where in ./ ../ ../../ ../../../ ../../../../ ../../../../../; do
+        if [ -e ${where}debian/rules -a -d ${where}debian/patches ]; then
+                export QUILT_PATCHES=debian/patches
+        fi
+    done
 
-     make -f debian/rules apply-patches
+To get the fully patched source after unpacking the source package, cd to
+the root level of the source package and run:
 
-   Note: It has been proposed that, in future, this should happen 
-   automatically when you run dpkg-source -x on a CDBS 
-   simple-patchsys.mk source package.  However, this proposal has 
-   apparently not yet been implemented, so for now you have to do 
-   it yourself like this.
+    quilt push -a
 
- * 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.patch, and then run:
+The last patch listed in debian/patches/series will become the current
+patch.
 
-     cdbs-edit-patch 01_add_README.source_file.patch
+To add a new set of changes, first run quilt push -a, and then run:
 
-   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).
+    quilt new <patch>
 
- * To remove source modifications that are currently being
-   applied when building the package, run:
+where <patch> is a descriptive name for the patch, used as the filename in
+debian/patches.  Then, for every file that will be modified by this patch,
+run:
 
-     make -f debian/rules reverse-patches
+    quilt add <file>
+
+before editing those files.  You must tell quilt with quilt add what files
+will be part of the patch before making changes or quilt will not work
+properly.  After editing the files, run:
+
+    quilt refresh
+
+to save the results as a patch.
+
+Alternately, if you already have an external patch and you just want to
+add it to the build system, run quilt push -a and then:
+
+    quilt import -P <patch> /path/to/patch
+    quilt push -a
+
+(add -p 0 to quilt import if needed). <patch> as above is the filename to
+use in debian/patches.  The last quilt push -a will apply the patch to
+make sure it works properly.
+
+To remove an existing patch from the list of patches that will be applied,
+run:
+
+    quilt delete <patch>
+
+You may need to run quilt pop -a to unapply patches first before running
+this command.




More information about the Python-apps-commits mailing list